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

76%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/java-test-updater/SKILL.md

Quality

Content

66%Weight 40%Scale 1-5

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

The content is highly actionable and well-sequenced with validation feedback loops, but it is verbose and monolithic: repetitive inline Java examples inflate token cost and nothing is split into reference files. Tightening examples and moving pattern catalogs to separate files would materially improve it.

Suggestions

Consolidate the repetitive before/after Java snippets in sections 3-7 and the 'Update Patterns' section, which largely duplicate each other, to reduce token cost.

Move the bulk of the worked-example patterns into a references file (e.g. PATTERNS.md) and keep SKILL.md as a concise overview pointing to it.

Trim prose that restates concepts Claude already knows (e.g. generic descriptions of what @BeforeEach or argument matchers do).

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose, repeating very similar Java before/after patterns across ten sections and an 'Update Patterns' section that largely restates earlier examples; much could be tightened or moved out.	2 / 5
Actionability	Provides numerous concrete, copy-paste-ready Java examples plus specific Maven/Gradle commands covering the common cases of signature, assertion, mock, and setup updates.	5 / 5
Workflow Clarity	A clearly sequenced 10-step workflow with explicit validation checkpoints (compile via mvn/gradlew, run tests, analyze failures) and a retry loop ('Repeat until all tests pass').	5 / 5
Progressive Disclosure	The skill is a monolithic single-file wall of code with no references, bundle files, or split-out detail material; content that belongs in separate reference files is fully inlined.	2 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it clearly states what the skill does, when to use it with concrete triggers, and covers several specific capabilities in third-person voice. Minor gaps in synonym/extension coverage keep trigger term quality and specificity just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Update Java test classes and methods', 'Handles method signature changes, class refactoring, assertion updates, and mock modifications') with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Update Java test classes and methods...') and when ('Use when code changes break existing tests due to signature changes, refactoring, or behavior modifications') with concrete triggers.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'signature changes, refactoring, or behavior modifications' and 'code changes break existing tests' are present, though synonyms and file extensions are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (updating Java tests after refactoring) with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 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	15 / 16 Passed

Repository: ArabelaTso/Skills-4-SE
Path: skills/java-test-updater/SKILL.md
Commit: 4f38503

Reviewed: 8 days 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.