regression-suite

Audit regression test suites for GDD critical path coverage gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents bug reintroductions and silent quality drift by ensuring every critical GDD path and every previously fixed bug remains covered by an appropriate regression test list.

Core Features & Use Cases

  • Critical-path coverage mapping: Audits GDD acceptance criteria against existing tests in tests/unit and tests/integration, flagging COVERED/PARTIAL/MISSING/EXEMPT gaps.
  • Fixed-bug regression verification: Scans closed bugs to determine whether a regression test exists that would catch the same failure scenario again.
  • Coverage drift detection: Detects when new systems, revised GDD sections, or completed sprint stories are not matched by added regression coverage, then produces a manifest update request.
  • Manifest maintenance: Updates or rewrites tests/regression-suite.md using a curated list that is safe to keep without removing existing entries.

Quick Start

Run regression-suite audit to generate a coverage status report and identify missing regression tests for GDD critical paths.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I keep regression testing coverage aligned with GDD critical paths?

To keep regression testing aligned with GDD critical paths, audit your test inventory against GDD acceptance criteria. This detects coverage drift by flagging COVERED, PARTIAL, MISSING, or EXEMPT gaps, ensuring critical systems remain tested.

How do I prevent fixed bugs from recurring in sprint-based workflows?

To prevent fixed bugs from recurring in sprint-based workflows, scan closed bug scenarios and map them to existing tests. If a matching test is missing, generate a manifest update request to add regression coverage for that specific failure.

What is regression coverage drift detection and when do I need it?

Regression coverage drift detection identifies when completed sprint stories or revised GDD sections lack matching regression tests. You need it when new systems are introduced, ensuring test manifests stay synchronized with evolving project requirements.

How do I update a regression suite manifest without removing existing entries?

To update a regression suite manifest without removing existing entries, rewrite the test regression-suite.md file using a curated list. This safely appends new coverage requirements while preserving the current audit history and test inventory.

Can I audit unit and integration tests against GDD acceptance criteria?

Yes, you can audit unit and integration tests against GDD acceptance criteria. The audit parses tests directories to map acceptance criteria and bug scenarios to existing tests, generating a comprehensive coverage status report.

What are the limitations of automated regression suite manifest maintenance?

Automated regression suite manifest maintenance relies on parsing existing test inventories and GDD structures. It cannot invent tests for undocumented paths and requires existing suite manifests to accurately detect coverage drift and generate status outputs.