regression-suite

Maps test coverage to GDD critical paths and maintains a regression suite manifest.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill regression-suite-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/regression-suite
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill regression-suite-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug fixes often ship without tests that would catch the original bug, and test coverage silently drifts as new game features are added. This Skill audits your test suite against GDD critical paths and closed bugs so regressions cannot silently return. ## Core Features & Use Cases - Critical Path Coverage Audit: Maps every GDD acceptance criterion, formula, and edge case to existing tests, classifying each as COVERED, PARTIAL, MISSING, or EXEMPT. - Bug Regression Tracking: Scans closed bugs in production/qa/bugs and flags any fix lacking a regression test, suggesting the exact test file path to create. - Coverage Drift Detection: Identifies new systems, completed stories, or revised GDD sections that have no corresponding test coverage. - Use Case: Before a release gate, run an audit to produce tests/regression-suite.md — a curated manifest of tests that must pass, known gaps, and quarantined flaky tests. ## Quick Start Run the regression suite audit to map my GDD critical paths against existing tests and update tests/regression-suite.md.

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 a bug fix has a regression test?

Run the update mode after fixing a bug. It scans closed bugs in production/qa/bugs, searches tests/unit and tests/integration for a matching test, and flags any fix missing regression coverage with a suggested test file path.

How to audit test coverage against game design documents?

Run audit mode to read design/gdd/systems-index.md and each MVP-tier system GDD. Every acceptance criterion, formula, and edge case is classified as COVERED, PARTIAL, MISSING, or EXEMPT, with a per-system coverage table.

What is the difference between update, audit, and report modes?

Update scans the current sprint's bug fixes and appends new entries to the manifest. Audit performs a full GDD-versus-tests coverage analysis and rewrites the manifest. Report is read-only and suitable for sprint reviews.

Does the regression suite delete or modify existing tests?

No. The manifest is append-only for existing entries and never removes registered tests without explicit approval. Flaky tests are quarantined in the manifest rather than deleted, and all writes require user confirmation first.

When should I run a regression coverage audit?

Run it after fixing a bug, before a release gate where the manifest is required, or at sprint close to detect coverage drift. A gap of more than two sprints since the last update flags the suite as likely stale.