java-test-updater
Updates broken JUnit tests after a deliberate code change — distinguishing tests that broke because the behavior changed (update assertion) from tests that broke because they were overcoupled to structure (loosen or delete). Use after API changes, refactors, or intentional behavior changes leave a trail of failing tests.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill java-test-updater97
Quality
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates a specific problem domain (fixing JUnit tests after intentional code changes), distinguishes between different failure modes, and provides explicit trigger conditions. The description uses third person voice correctly and includes natural developer terminology that would match real user queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'update assertion', 'loosen or delete' tests, and distinguishes between behavior-changed tests vs overcoupled tests. Clear domain (JUnit tests) with specific scenarios. | 3 / 3 |
Completeness | Clearly answers both what ('Updates broken JUnit tests...distinguishing tests that broke because behavior changed from overcoupled tests') AND when ('Use after API changes, refactors, or intentional behavior changes leave a trail of failing tests'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'JUnit tests', 'API changes', 'refactors', 'failing tests', 'broken tests', 'behavior changes'. Good coverage of terms developers naturally use when facing this problem. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: JUnit test updates after deliberate code changes. Unlikely to conflict with general testing skills or code refactoring skills due to the precise focus on test repair after intentional changes. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that provides clear, actionable guidance for a complex judgment-heavy task. The triage-first approach with explicit regression detection is well-designed, and the concrete examples with git blame context demonstrate exactly how to apply the guidance. The 'Do not' section effectively constrains dangerous behaviors.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with actionable tables, concrete examples, and no explanation of concepts Claude already knows. The skill assumes competence and delivers dense, useful information without padding. | 3 / 3 |
Actionability | Provides executable commands, concrete Java code examples with before/after patterns, specific git commands, and detailed tables mapping failure causes to actions. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Clear 3-step sequence (separate breaks → compile fixes → assertion triage) with explicit validation checkpoint: identifying regressions before any updates. The 'regression trap' section serves as a critical feedback loop preventing premature changes. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and tables, but the skill is self-contained with no references to external files. For a skill of this length (~150 lines), some content like the over-coupling patterns table could be split to a reference file. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.