interval-guided-regression-test-update
Automatically updates regression tests based on interval analysis to maintain coverage of key program intervals. Use when code changes affect value ranges, conditionals, or control flow, and existing tests need updating to maintain interval coverage. Analyzes interval information from updated code, identifies coverage gaps, adjusts test inputs and assertions, removes redundant tests, and generates new tests for uncovered intervals. Supports Python, Java, JavaScript, and C/C++ with various test frameworks (pytest, JUnit, Jest, Google Test).
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill interval-guided-regression-test-update82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%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-structured description that clearly explains what the skill does and when to use it, with good specificity about supported languages and frameworks. The main weakness is the use of technical jargon ('interval analysis', 'interval coverage') that users may not naturally use when requesting help, which could reduce discoverability. The description would benefit from including more common user-facing terms alongside the technical terminology.
Suggestions
Add more natural trigger terms users might say, such as 'update tests after refactoring', 'fix test coverage', 'tests failing after code changes', or 'maintain test suite'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyzes interval information', 'identifies coverage gaps', 'adjusts test inputs and assertions', 'removes redundant tests', 'generates new tests'. Also specifies supported languages and frameworks. | 3 / 3 |
Completeness | Clearly answers both what ('updates regression tests based on interval analysis') and when ('Use when code changes affect value ranges, conditionals, or control flow, and existing tests need updating'). Has explicit 'Use when...' clause with specific trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'regression tests', 'interval analysis', 'coverage', 'pytest', 'JUnit', 'Jest', but uses technical jargon ('interval analysis', 'interval coverage') that users may not naturally say. Missing common variations like 'unit tests', 'test updates', 'fix failing tests'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche focusing on 'interval analysis' for test maintenance, which is distinct from general testing skills. The combination of interval-based coverage analysis and automatic test updates creates a clear, unique domain unlikely to conflict with other testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for interval-guided test updates with good code examples and clear structure. However, it's somewhat verbose with repetitive examples and explanations of concepts Claude already knows. The workflow would benefit from more explicit validation checkpoints, especially given the potentially destructive nature of removing or modifying tests.
Suggestions
Condense the three 'Quick Start Examples' into one comprehensive example, or move additional examples to a separate reference file
Remove or significantly shorten the 'Core Concept' section - Claude understands intervals and can infer the concept from examples
Add explicit validation checkpoints in the workflow, particularly a 'verify before removing' step when removing redundant tests
Consolidate the 'Best Practices', 'Tips', and 'Troubleshooting' sections which have overlapping content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation of basic concepts (what intervals are, basic coverage calculations) that Claude would already understand. The examples are helpful but repetitive - three similar examples showing interval changes could be condensed. The 'Core Concept' section explaining intervals is somewhat verbose. | 2 / 3 |
Actionability | The skill provides concrete, executable Python code examples throughout. The workflow steps are specific with clear code snippets showing before/after states. The examples are copy-paste ready and demonstrate real transformations. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced, but validation is mentioned only briefly in step 5 without explicit checkpoints or feedback loops. For a skill involving test modifications (potentially destructive), there should be more explicit validation gates between steps, especially before removing tests. | 2 / 3 |
Progressive Disclosure | The skill has a clear structure with a quick start section, detailed strategies, and appropriate references to external files (interval-analysis.md, test-update-strategies.md) for deeper content. Navigation is well-signaled and references are one level deep. | 3 / 3 |
Total | 10 / 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.