regression-suite

Map test coverage to GDD critical paths and identify missing regression tests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill regression-suite-nevesb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/regression-suite
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill regression-suite-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that bug fixes are accompanied by tests that would have caught the original failures and that a curated regression-suite manifest accurately maps test coverage to GDD critical paths, preventing silent regressions and coverage drift as the game evolves.

Core Features & Use Cases

  • Audit GDD vs tests: Scan design GDD acceptance criteria and map them to existing unit, integration, and regression tests to identify missing coverage.
  • Verify bug fixes: Inspect closed bug reports to confirm whether a regression test was added when a bug was fixed and flag missing tests with suggested file paths.
  • Detect coverage drift: Find new stories or systems added without corresponding tests and flag stale manifests when last-updated dates lag sprint cadence.
  • Manifest management: Generate or update tests/regression-suite.md with a curated registry of regression tests, quarantined tests, known gaps, and run-mode reports; always ask for write permission before modifying the manifest.

Quick Start

Run /regression-suite update after closing a bug to scan for missing regression tests and propose updates to 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 map regression tests to GDD critical paths in a game development repository?

To map regression tests to GDD critical paths, scan design GDDs, sprint stories, and bug reports to extract acceptance criteria, then use file globbing and grep to match existing tests against those paths and identify missing coverage.

How do I verify a closed bug fix has a corresponding regression test?

To verify a closed bug fix has a regression test, inspect closed bug reports to extract metadata, then scan the test suite to confirm a test was added that would catch the original failure, flagging any missing tests with suggested file paths.

What is a regression-suite manifest and when do I need to update it?

A regression-suite manifest is a curated registry of regression tests, quarantined tests, and known gaps mapping coverage to GDD paths. Update it after closing a bug or during release gate workflows to prevent coverage drift as the game evolves.

How do I detect test coverage drift for new game systems or sprint stories?

Detect test coverage drift by scanning newly added sprint stories and design GDD acceptance criteria, then comparing them against existing unit, integration, and regression tests to flag any systems lacking corresponding test files.

Can I automate generating a regression test manifest without manually writing markdown?

Yes, you can automate manifest generation by scanning tests and docs to categorize coverage statuses, then automatically writing a curated tests/regression-suite.md file with run-mode reports after explicitly asking for user write approval.

Does regression testing for game development work without external test frameworks?

Regression testing for game development works by applying file globbing and grep across tests and docs to extract acceptance criteria and bug metadata, operating directly within the repository without requiring external framework dependencies.