java-regression-test-generator

Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions. Use when users need to: (1) Generate tests after refactoring or code changes, (2) Ensure previously tested behavior still works in new versions, (3) Cover modified or newly added code paths, (4) Migrate existing tests to work with updated APIs or signatures, (5) Maintain test coverage during code evolution. Supports JUnit and TestNG frameworks with unit tests, parameterized tests, and exception testing patterns.

1.00x

Quality

78%

Does it follow best practices?

Impact

76%

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-regression-test-generator/SKILL.md

Quality

Content

61%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.

Highly actionable content with executable examples and a clear workflow, but it is verbose for the token budget and lacks an inline compile/run validation checkpoint in the generation flow. Offloading the worked examples into the existing references would improve both conciseness and progressive disclosure.

Suggestions

Move two of the three full worked examples into references/change_patterns.md or a new examples file, keeping only one representative example inline in SKILL.md to cut roughly half the body length.

Add an explicit Step 6 validation checkpoint (e.g., 'Compile generated tests with the new code; if compilation or assertions fail, fix and regenerate') with a fix-and-retry loop instead of leaving verification only in Tips.

Trim obvious Tips such as 'Use appropriate mocks' and 'Maintain readability' that restate knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	The ~550-line body is noticeably verbose: three full worked examples each reproduce complete old/new/test code demonstrating well-known JUnit/mocking/Optional patterns Claude already knows, and the Tips section states obvious guidance ("Use appropriate mocks", "Maintain readability").	2 / 5
Actionability	Provides fully executable, copy-paste-ready Java test code across multiple change scenarios, a concrete change-type-to-strategy table, and a clear output template covering the common cases.	5 / 5
Workflow Clarity	A clear five-step sequence with a strategy table is present, but validation/verification (e.g., confirm generated tests compile and pass) lives only in Tips rather than as an explicit checkpoint with a fix-and-retry feedback loop in the batch generation flow.	3 / 5
Progressive Disclosure	Good structure with a References section and inline links to two real one-level-deep files (change_patterns.md, test_patterns.md); minor gap is that the three large worked examples are inlined in SKILL.md rather than pushed into those references.	4 / 5
	Total	14 / 20 Passed

Description

88%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.

A strong, concrete description that explicitly states both what the skill does and when to use it, with mostly natural trigger terms and a clear niche. Slight room to add file-extension/synonym triggers and tighten distinctiveness from general test generation.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (generate regression tests, analyze changes between versions, migrate tests, cover modified paths) plus concrete framework/coverage details (JUnit/TestNG, parameterized and exception tests), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers "what" (generate regression tests by analyzing changes between old and new versions) and "when" (a numbered "Use when users need to" list with concrete trigger phrases).	5 / 5
Trigger Term Quality	Strong natural terms ("regression tests", "refactoring", "code changes", "migrate existing tests", "JUnit", "TestNG") that users would actually say, but misses common synonyms/extensions like ".java files" so a few natural terms are absent.	4 / 5
Distinctiveness Conflict Risk	The version-comparison regression-testing niche is clearly distinct, but triggers like "Generate tests after refactoring" have minor overlap risk with general Java test-generation skills.	4 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (554 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

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

Reviewed: 11 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.