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).

0.92x

Quality

74%

Does it follow best practices?

Impact

88%

0.92x

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/interval-guided-regression-test-update/SKILL.md

Quality

Content

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

Well-structured and largely actionable with clear references and a validated workflow, but materially over-long due to redundant examples and sections that restate the same process. Tightening would improve token efficiency without losing clarity.

Suggestions

Consolidate the three near-identical Quick Start examples into one and move the others into references/test-update-strategies.md; similarly fold Update Strategies and Common Scenarios into that reference to avoid restating the 6-step workflow.

Drop the 'Core Concept' explanation of what intervals/value ranges are — Claude already knows this — and keep only the interval-testing-specific framing.

Replace the comment-only guidance in 'Update Tests' (e.g. '# If boundary changed from x < 10 to x < 20') with concrete executable test snippets matching the Quick Start examples.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: three near-identical Quick Start worked examples, an Update Strategies section that restates the workflow's Step 4, plus Common Scenarios and Troubleshooting that re-derive the same 6-step process, and a Core Concept paragraph explaining value ranges Claude already knows.	2 / 5
Actionability	The Quick Start examples are concrete, executable Python test functions covering common cases, though the core 'Update Tests' step relies on comment/pseudocode guidance ('# If boundary changed...') rather than runnable snippets.	4 / 5
Workflow Clarity	A clear six-step sequence with an explicit validation step (Step 5: execute, verify pass, check coverage, find gaps) for this batch operation; the validate→fix→retry loop is only weakly signaled inside the workflow itself (delegated to the Troubleshooting section).	4 / 5
Progressive Disclosure	Two real one-level-deep references (interval-analysis.md, test-update-strategies.md) are clearly signaled inline and summarized in a References section, but the ~490-line body retains substantial detail that could live in those reference files.	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, specific description that clearly states capabilities and an explicit use-trigger. It is mostly distinct and well-targeted, with only minor room to broaden trigger synonyms and reduce niche jargon.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'analyzes interval information', 'identifies coverage gaps', 'adjusts test inputs and assertions', 'removes redundant tests', 'generates new tests for uncovered intervals' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both what ('Automatically updates regression tests...') and when ('Use when code changes affect value ranges, conditionals, or control flow, and existing tests need updating...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural triggers like 'code changes affect value ranges, conditionals, or control flow' and 'existing tests need updating' plus concrete framework names, but 'interval analysis/coverage' is fairly technical jargon and synonyms like 'test coverage' are underrepresented.	4 / 5
Distinctiveness Conflict Risk	The interval-guided framing is a distinct niche, but the triggers around updating tests after code changes carry minor overlap risk with a general regression-test-updating skill.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ArabelaTso/Skills-4-SE
Path: skills/interval-guided-regression-test-update/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.