Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/regression-suite
Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.
Passed 14 of 18 test cases with the skill, and 5 of 18 without it.
and 16 more in the full report
10 fixed4 passed either way3 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We ran /regression-suite update and reviewed the generated recommendations. When asked for permission to update tests/regression-suite.md, the user declined the file write. What is the final status verdict?
| Checked | Without skill | With skill |
|---|---|---|
| Does not write or modify tests/regression-suite.md | Passed | Passed |
| Outputs verdict BLOCKED | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,qa.level,system_overrides
Resolved above — use as-is. No block → defaults in
.claude/docs/config-resolution.md.
This skill ensures that every bug fix is backed by a test that would have caught the original bug — and that the regression suite stays current as the game evolves. It also detects when new features have been added without corresponding regression coverage.
A regression suite is not a new test category — it is a curated list of
tests already in tests/ that collectively cover the game's critical paths
and known failure points. This skill maintains that list.
Output: tests/regression-suite.md
When to run:
qa.level: full, /gate-check requires a regression suiteEvery AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Workflow tier: modes.workflow as resolved above — supplied by modes.rigor
unless set explicitly — per .claude/docs/workflow-modes.md; in audit mode consider
workflow_overrides.system_overrides.<system> per system as each GDD is read. It
sets whether GDD critical paths are mapped or coverage is smoke-only — see Step 2c.
qa.level: controls whether the suite is generated at
all. At minimal, the regression suite is not generated (report that and
stop); at standard, generate it at Polish-stage entry; at full, at
Production-stage entry. Distinct axis from workflow.
test cases passed, vs 5 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.