tracking-regression-tests
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-regression-testsThis 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill content is overly verbose, explaining concepts Claude already understands while failing to provide concrete, executable guidance. It describes what the skill does conceptually but never shows actual commands, plugin usage syntax, expected outputs, or error handling. The content reads more like documentation for a human user than actionable instructions for Claude.
Suggestions
Replace abstract descriptions with concrete, executable commands showing exact syntax for the regression-test-tracker plugin (e.g., `regression-test-tracker run`, `regression-test-tracker mark test_name`)
Remove the Overview, 'How It Works', and 'Best Practices' sections—Claude doesn't need explanations of what regression testing is or why it matters
Add example outputs showing what successful runs and failures look like, so Claude knows how to interpret and report results
Include specific error handling guidance: what to do when tests fail, how to identify flaky tests, and how to report findings to the user
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what regression tests are, why they matter, general best practices). The 'Overview' and 'How It Works' sections add little actionable value and could be eliminated entirely. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The examples describe what the skill 'will do' in abstract terms rather than showing actual commands, expected outputs, or how to use the 'regression-test-tracker' plugin. | 1 / 3 |
Workflow Clarity | Steps are listed in 'How It Works' but lack specificity—no actual commands, no validation checkpoints, and no error handling guidance. The workflow is conceptual rather than operational. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one file. The 'Integration' section hints at more but provides no references. For a skill of this length, the structure is acceptable but the content itself is padded. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%This is a well-crafted skill description that clearly communicates its purpose and includes explicit trigger conditions. The description effectively covers what the skill does and when to use it, with good trigger term coverage. Minor improvement could be made by being more specific about some capabilities like 'analyzing the impact of changes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (regression testing) and lists several actions (track tests, run tests, identify critical tests, analyze impact, provide test history, identify flaky tests), but some actions are somewhat vague like 'maintaining code stability' and 'analyzing the impact of changes'. | 2 / 3 |
Completeness | Clearly answers both what (track and run regression tests, identify critical tests, analyze impact, provide test history, identify flaky tests) AND when ('triggered when the user asks to track regression, run regression tests, or uses the shortcut reg'). | 3 / 3 |
Trigger Term Quality | Explicitly includes natural trigger terms users would say: 'track regression', 'run regression tests', and the shortcut 'reg'. These are specific phrases a user 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 skills due to the specific regression focus and explicit trigger terms. | 3 / 3 |
Total | 11 / 12 Passed |
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.