regression-suite

Map GDD critical paths and fixed bugs to existing test coverage.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill regression-suite-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/regression-suite
Command: npx skills add https://github.com/easonlao/jiazi-game --skill regression-suite-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents bugs from silently returning by ensuring fixes are backed by regression tests, and it helps detect when new features or GDD changes outpace the existing test coverage.

Core Features & Use Cases

  • Critical-path mapping to tests: Audits GDD acceptance criteria and maps them to existing unit/integration tests to identify COVERED, PARTIAL, MISSING, or EXEMPT areas.
  • Fixed-bug regression verification: Scans closed/fixed bugs and checks whether each has a corresponding regression guard in tests/.
  • Coverage drift detection: Flags likely staleness when the suite manifest is outdated, new systems/stories lack coverage, or new GDD sections appear without matching regression updates.
  • Suite manifest maintenance: Produces and/or updates tests/regression-suite.md as a curated registry of regression tests to require for release gates.

Quick Start

Run /regression-suite audit to generate an end-to-end status report of critical path coverage and identify regression gaps before the next release gate.

Frequently Asked Questions about regression-suite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my test coverage includes regression tests for fixed bugs?

To check regression test coverage for fixed bugs, scan closed bug reports in production/qa/bugs/*.md and verify each has a corresponding regression guard in the tests/ directory. This audit identifies whether bug fixes are backed by tests to prevent silent regressions.

What is coverage drift detection in regression testing?

Coverage drift detection flags staleness when the suite manifest is outdated, new systems or stories lack matching tests, or new GDD sections appear without regression updates. It ensures test coverage keeps pace with design changes and feature additions.

How do I map GDD critical paths to existing test coverage?

Map GDD critical paths to existing tests by parsing design/gdd/systems-index.md and auditing acceptance criteria against unit and integration tests. This classifies coverage status as COVERED, PARTIAL, MISSING, or EXEMPT to find missing regression protection.

When should I run a regression suite audit for release gates?

Run a regression suite audit during release gates, sprint closeouts, and post-fix workflows. This identifies coverage drift or missing regression tests before deployment, ensuring critical paths remain safe and the suite manifest is updated.

Can I update the regression suite manifest automatically after an audit?

Yes, the regression suite manifest can be updated by running the audit in update mode. This modifies tests/regression-suite.md to serve as a curated registry of regression tests required for release gates.

What are the limitations of auditing regression coverage without a GDD?

Without parsing design/gdd/systems-index.md and test inventories, the audit cannot map critical paths or detect coverage drift. The regression suite requires these files to classify coverage status and identify missing regression protection accurately.