tracking-regression-tests
This skill enables Claude to track and run regression tests, ensuring new changes don't break existing functionality. It is triggered when the user asks to "track regression", "run regression tests", or uses the shortcut "reg". The skill helps in maintaining code stability by identifying critical tests, automating their execution, and analyzing the impact of changes. It also provides insights into test history and identifies flaky tests. The skill uses the `regression-test-tracker` plugin.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-regression-tests87
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/skillEvaluation — 92%
↑ 1.39xAgent success when using this skill
Validation for skill structure
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 a well-crafted skill description that clearly articulates specific capabilities (tracking, running, analyzing regression tests), includes explicit trigger conditions with natural user terms, and maintains a distinct focus on regression testing. The description uses proper third-person voice and provides comprehensive coverage of both what the skill does and when to use it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'track and run regression tests', 'identifying critical tests', 'automating their execution', 'analyzing the impact of changes', 'provides insights into test history', 'identifies flaky tests'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('track and run regression tests, identifying critical tests, automating execution, analyzing impact, test history insights, flaky test identification') and when ('triggered when the user asks to track regression, run regression tests, or uses shortcut reg'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'track regression', 'run regression tests', and the shortcut 'reg'. These are practical terms developers would naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on regression testing with distinct triggers ('regression', 'reg' shortcut). Unlikely to conflict with general testing or code quality skills due to the specific 'regression' focus and explicit trigger terms. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content reads more like a feature description than actionable instructions for Claude. It lacks concrete commands, executable examples, and specific plugin syntax. The content explains concepts Claude already understands while omitting the actual implementation details needed to use the regression-test-tracker plugin.
Suggestions
Replace abstract examples with concrete, executable commands showing actual plugin syntax (e.g., `regression-test-tracker run --suite=critical` or whatever the actual CLI is)
Remove the Overview section explaining what regression tests are - Claude knows this. Start directly with usage instructions.
Add actual output examples showing what test results look like and how to interpret them
Include the specific flags, options, and configuration for the regression-test-tracker plugin rather than describing behavior abstractly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what regression tests are, why they're important). Phrases like 'crucial for maintaining software quality' and the entire Overview section add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The examples describe what 'the skill will do' abstractly rather than showing actual commands or plugin usage syntax. Missing: actual CLI commands, expected output formats, or plugin API calls. | 1 / 3 |
Workflow Clarity | Steps are listed in 'How It Works' but lack specificity. No validation checkpoints, no error handling guidance, and no concrete commands for each step. The workflow is conceptual rather than executable. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one file. No references to external documentation for the regression-test-tracker plugin, advanced configuration, or detailed API reference that would benefit from separation. | 2 / 3 |
Total | 6 / 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.