java-test-updater

Update Java test classes and methods to work with new code versions after refactoring or modifications. Use when code changes break existing tests due to signature changes, refactoring, or behavior modifications. Takes old and new code versions plus old tests as input, and outputs updated tests that compile and pass against the new code. Handles method signature changes, class refactoring, assertion updates, and mock modifications.

1.00x

Quality

88%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, actionable skill with excellent workflow clarity and concrete code examples. The main weakness is verbosity - the document is comprehensive but could be more token-efficient by assuming Claude's Java knowledge and potentially splitting detailed patterns into a separate reference file. The validation steps and feedback loops are well-implemented.

Suggestions

Move the 'Update Patterns' section to a separate PATTERNS.md file and reference it from the main skill to improve progressive disclosure

Trim the 'Tips' section - most items (use IDE tools, compile frequently, maintain coverage) are standard practices Claude already knows

Consolidate repetitive examples in sections 3-5 where similar update patterns are shown multiple times with slight variations

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some redundancy. The extensive code examples are valuable, but some explanations are verbose (e.g., listing all change categories, repeating similar patterns). The 'Tips' section contains advice Claude already knows.	2 / 3
Actionability	Excellent actionability with fully executable Java code examples throughout. Every step includes concrete, copy-paste ready code snippets showing both old and updated versions. The patterns section provides complete before/after examples.	3 / 3
Workflow Clarity	Clear 10-step workflow with explicit validation checkpoints (Step 8: Verify Compilation, Step 9: Run and Verify Tests). Includes feedback loops ('If tests fail' with numbered recovery steps) and bash commands for verification.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections and headers, but it's a monolithic document that could benefit from splitting detailed patterns into a separate reference file. The 'Update Patterns' section alone is substantial and could be externalized.	2 / 3
	Total	10 / 12 Passed

Description

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 a well-crafted skill description that excels across all dimensions. It clearly specifies the domain (Java test updates), provides concrete actions (signature changes, assertion updates, mock modifications), includes an explicit 'Use when...' clause with natural trigger terms, and maintains a distinct niche that won't conflict with general coding skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Update Java test classes and methods', 'handles method signature changes, class refactoring, assertion updates, and mock modifications'. Clear input/output specification provided.	3 / 3
Completeness	Clearly answers both what ('Update Java test classes...handles method signature changes, class refactoring, assertion updates, and mock modifications') AND when ('Use when code changes break existing tests due to signature changes, refactoring, or behavior modifications').	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'Java test', 'refactoring', 'tests', 'signature changes', 'mock modifications', 'compile and pass'. Good coverage of terms developers use when dealing with broken tests.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on Java test updates after code changes. The combination of 'Java', 'test', 'refactoring', and 'old/new code versions' creates a distinct trigger profile unlikely to conflict with general coding or testing skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (518 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: ArabelaTso/Skills-4-SE
Commit: 0f00a4f

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

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.