regression-suite

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

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

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 existing tests against GDD critical paths and closed bugs, then maintains a curated regression suite manifest so releases are protected against known failure points. ## Core Features & Use Cases - Critical Path Coverage Audit: Maps every GDD acceptance criterion to existing unit and integration tests, classifying each as COVERED, PARTIAL, MISSING, or EXEMPT. - Bug Regression Detection: Scans closed bug reports and flags any fix lacking a test that would catch recurrence, 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 listing all registered regression tests, known gaps, and quarantined flaky tests, with HIGH priority flags on formula and state-machine paths. ## Quick Start Ask the AI to run the regression suite audit to map GDD critical paths against existing tests and update tests/regression-suite.md with any missing regression coverage.

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 bug reports in production/qa/bugs, searches test directories for a test referencing the bug ID or failure scenario, and flags any fix missing regression coverage with a suggested test file path.

How to audit test coverage against game design requirements?

Run audit mode to read every GDD acceptance criterion, formula, and edge case, then classify each as COVERED, PARTIAL, MISSING, or EXEMPT based on existing unit and integration tests. Missing formula or state-machine paths are elevated to HIGH priority gaps.

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, producing a status summary suitable for sprint reviews without writing files.

Does the regression suite replace writing new tests?

No. The suite is a curated manifest of tests already in the tests directory, not a new test category. It registers which existing tests must pass before release and lists gaps where tests should be written, which can be scaffolded with a test-helpers skill.

What happens to flaky tests in the regression suite?

Flaky or intermittently failing tests are quarantined in the manifest with a reason and date rather than deleted. They are excluded from CI runs but remain registered so they can be fixed later by a test-flakiness workflow.