java-regression-test-generator
Generates JUnit regression tests that lock in current behavior before a refactor, capturing observed outputs as assertions so that any behavioral change trips a test. Use before large refactors, when inheriting untested legacy Java, or when the spec is "whatever it does now."
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill java-regression-test-generator97
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 use case (characterization/regression testing before refactoring Java code), uses natural language triggers, and explicitly states both capabilities and when to use them. The description is concise yet comprehensive, with the colloquial 'whatever it does now' phrase adding memorable distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Generates JUnit regression tests', 'lock in current behavior', 'capturing observed outputs as assertions', 'behavioral change trips a test'. Multiple specific actions clearly described. | 3 / 3 |
Completeness | Clearly answers both what ('Generates JUnit regression tests that lock in current behavior...capturing observed outputs as assertions') AND when ('Use before large refactors, when inheriting untested legacy Java, or when the spec is whatever it does now'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'JUnit', 'regression tests', 'refactor', 'legacy Java', 'untested'. The phrase 'whatever it does now' captures informal user language effectively. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: specifically JUnit, specifically regression/characterization tests for pre-refactor scenarios, specifically Java legacy code. Unlikely to conflict with general testing or other language testing skills. | 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 a high-quality skill that provides concrete, actionable guidance for generating Java regression tests. The workflow is clear, examples are executable, and the 'do not' section provides valuable guardrails. The only minor weakness is that cross-references to related skills could be more prominently organized for navigation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Java and testing concepts. No unnecessary explanations of what regression tests are at a basic level—jumps straight to actionable guidance with well-chosen examples. | 3 / 3 |
Actionability | Provides fully executable JUnit 5 code examples, specific patterns for parameterized tests, concrete strategies for handling non-determinism, and clear 'do not' constraints. Every section gives copy-paste ready guidance. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow (pick capture points → generate inputs → capture and emit → handle non-determinism) with explicit decision criteria at each step. The 'When regression tests are the right tool' table provides upfront validation of whether to proceed. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but references to other skills (`unit-test-generator`, `coverage-enhancer`, `mocking-test-generator`) are inline mentions rather than clearly signaled navigation. The skill is appropriately self-contained but could better signal these cross-references. | 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.