By tanerilyazovUpdated 2026-05-11java-change-with-tests@clawhub_tanerilyazov/java-change-with-tests
Code GenerationTest Generation
According to AlphaMoat, as of 2026-09, Java changing with tests has 3,531 downloads and 1 stars — ranked #3,116 of 5,078 AI skills overall, and #399 of 577 in Development.
| Platform | Installs | Downloads | Stars | Comments |
|---|---|---|---|---|
| ClawHub ↗ | 101 | 3.1K | 1 | - |
| SkillHub ↗ | 160 | 3.5K | 1 | — |
Platforms count differently and update at different times.
It requests acceptance criteria, module context and build/test conventions, then plans a small diff, implements it, runs targeted tests and reports exact commands and results. Confirm whether integration tests are required. Use only repositories where edits and build/test execution are intended. Targeted tests cover the stated scope; report remaining risks and follow-ups.
Profile published 2026-10-27
Generated from the skill’s documentation as examples; not results of actual runs.
The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.
| Month | Downloads | MoM | Stars |
|---|---|---|---|
| 2026-09 | 3.5K | — | 1 |
| 2026-08 | 3.2K | +5.6% | 1 |
| 2026-07 | 3.0K | +9.5% | 1 |
| 2026-06 | 2.7K | +6.4% | 1 |
| 2026-05 | 2.6K | — | 1 |
| 2026-03 | 2.3K | — | 1 |
The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.
# java-change-with-tests ## When to use - Any Java change that must be merged safely (feature/refactor/bugfix). ## Inputs to request (if missing) - Acceptance criteria (1-3 bullets). - Module name (if multi-module repo). - Build tool and test conventions. - Whether integration tests are required for the change.
## Steps 1. Repo map (brief): identify the module, entrypoint, and test location. 2. Plan: smallest diff that meets acceptance criteria. 3. Implement: minimal edits. 4. Tests: - prefer fast unit tests first - add integration tests only when required to validate behavior 5. Verify: - run targeted tests - run `mvn -q test` (or module-scoped equivalent) 6. Output PR-ready summary with evidence. ## Verification commands (project-specific) - Use the repo's build tool and record the exact commands and results. - Prefer targeted unit tests before full test suites. ## Output contract 1) Plan (3-6 steps) 2) Files changed + intent 3) Commands run + results 4) Risks + follow-ups
A skill for working with GitHub through the gh CLI: pull request checks, workflow runs, and API queries.
A search skill that aggregates 16 engines and needs no API key.
Lists, configures, authorizes and calls MCP servers and tools from the command line.
Generate valid Mermaid diagrams like flowcharts, sequence diagrams, mind maps, ER diagrams, or user journeys from text or product descriptions.
Access the YouTube Data API through managed OAuth to search videos and manage channel content.
Accesses the GitHub REST API over a managed OAuth connection.
A coding workflow skill covering planning, implementation, verification, and testing.
A skill that collects essential Docker commands and container workflows.
Data month: 2026-09 · Downloads, stars and installs are aggregated monthly from public skill registries (ClawHub, SkillHub). See methodology.