skills.rest
dnkrow
dnkrowCOMMUNITY
Explore all skills by this author →
GitHub

regression-suite

Map regression coverage to GDD acceptance criteria and closed-bug fixes.

1|Updated May 15, 2026
Search Tags:#regression testing#GDD#release gate#test manifest#bug validation#coverage audit
One-click install
npx skills add https://github.com/dnkrow/skill --skill regression-suite-dnkrow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/dnkrow/skill/tree/main/claude-global/regression-suite
Command: npx skills add https://github.com/dnkrow/skill --skill regression-suite-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents bugs from silently returning by ensuring each fix maps to an existing (or newly registered) regression test and by detecting coverage drift when the game evolves.

Core Features & Use Cases

  • Critical path coverage audit: Compares GDD acceptance criteria and edge cases against existing unit/integration/regression tests to flag missing or partial coverage.
  • Fixed-bug regression validation: Checks closed or fixed bugs and verifies whether a regression test exists that would catch the same failure scenario again.
  • Regression suite manifest maintenance: Updates or rewrites tests/regression-suite.md with gaps, quarantined indicators, and actionable recommendations for new tests.

Quick Start

Run /regression-suite audit to produce a coverage and gap report for the current GDD critical paths and recently fixed bugs.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I map regression test coverage to GDD acceptance criteria?▼

Map regression test coverage by scanning unit, integration, and regression test inventories and comparing them against critical paths extracted from design/gdd/systems-index.md. This flags missing or partial coverage for GDD acceptance criteria and edge cases.

How do I verify if a regression test exists for a fixed bug?▼

Verify fixed-bug regression coverage by checking closed or fixed bugs and scanning existing test inventories to confirm whether a regression test exists that would catch the same failure scenario again.

When should I run a regression coverage audit during a sprint?▼

Run a regression coverage audit during sprint-level workflows after bug fixes or before release gates to detect missing, partial, or drifted coverage and ensure critical paths remain covered.

What is a regression suite manifest and how is it maintained?▼

A regression suite manifest is a tests/regression-suite.md file updated with coverage gaps, quarantined indicators, and actionable recommendations for new tests. It is rewritten only when approved for write modes.

Does the regression suite audit require specific design documents?▼

Yes, the audit requires reading tests/regression-suite.md when present and extracting critical paths from design/gdd/systems-index.md along with linked systems to evaluate coverage accurately.

What is the best way to detect coverage drift after a game evolves?▼

Detect coverage drift by applying a regression suite audit that compares GDD critical acceptance criteria against existing unit, integration, and regression tests to flag missing, partial, or drifted coverage.

Related Skills

Explore More Software Engineering Skills→
XGanQAQXGanQAQ
1

regression-suite

Map GDD critical paths and closed bugs to existing unit and integration test coverage.

Community
Advanced
brand6brand6

regression-suite

Audit tests against GDD key paths and update the regression registry.

Community
Advanced
MichaelSolatiMichaelSolati

regression-suite

Align game regression tests with GDD critical paths and closed bug fixes.

Community
Advanced
scomofoscomofo

regression-suite

Audit regression test coverage against GDD critical paths and closed bug fixes.

Community
Advanced