increment-code-unit-test-creatUse when generating JUnit 5 + Mockito unit tests for Java/Maven source code, especially for incremental changes on a git branch. Activates when user asks to...
Install via ClawdBot CLI:
clawdbot install endcy/increment-code-unit-test-creatGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Sep 28, 2026
A developer finishes a refactor or feature on a git branch and wants unit tests only for what changed. The skill diffs the current branch against main/master, isolates new or modified methods, and generates JUnit 5 + Mockito tests targeting those methods without duplicating existing coverage.
A legacy service contains classes with little to no unit tests and a dangerous default branch. The developer points the skill at specific classes or packages, and it performs full-class test generation with a 90-100% target, using mocks to isolate database, Redis, HTTP, and MQ dependencies so tests are deterministic and runnable in CI.
A team ships dozens of small backend commits per day across multiple repositories. Integrating this skill into a pre-commit or CI workflow means every change that touches src/main/java automatically gets fresh unit tests before merge, keeping method coverage consistently high without a separate QA step.
A new backend engineer joins a project, picks up a ticket on an unfamiliar module, and uses the skill to generate tests that double as executable documentation. Because it reads dependent classes, DTOs, and Lombok annotations first, the generated tests reconstruct realistic inputs and reveal hidden constraints such as disabled setters or computed getters.
A developer maintains a service where every method calls out to payment gateways, message brokers, or external APIs. The skill's full-mock strategy produces Mockito-based tests that simulate every external dependency, making it possible to test business logic in isolation without flaky network calls or shared test databases.
A monthly seat-based subscription for engineering teams that want automated incremental test authoring embedded into their local IDE, CI, or coding assistant. Value is measured by reduced time spent writing boilerplate tests and increased coverage across every pull request.
Sold as a paid integration or plugin for existing CI platforms (GitHub Actions, GitLab CI, Jenkins, or cloud build tools). Customers pay per build minutes, per repository, or per generated test execution, tying revenue directly to the volume of code merged.
A high-touch engagement where the vendor deploys the skill alongside consulting, custom rule configuration, and coverage dashboards for regulated industries. Revenue comes from annual contracts, compliance audits, and ongoing support rather than pure software licensing.
💬 Integration Tip
Hook the skill into your pre-commit hooks or CI pipeline so every push against a main/master baseline automatically triggers incremental test generation, then gate merges on the JaCoCo coverage threshold. Ensure the CI runner has Git and Maven and that pom.xml test dependencies match the project JDK version to avoid Mockito class-version failures.
Scored Sep 28, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.