regression-suite

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill makes sure bug fixes are protected by automated regression tests by mapping the existing test inventory to GDD critical paths and closed bug fixes, surfacing gaps and coverage drift so regressions cannot silently return.

Core Features & Use Cases

  • Audit GDD Acceptance Criteria: map acceptance criteria to unit and integration tests and mark each as COVERED, PARTIAL, MISSING, or EXEMPT.
  • Verify Bug Fixes: scan production/qa/bugs for closed bugs and detect whether a corresponding regression test exists, suggesting file paths for missing tests.
  • Maintain a Manifest: create or update tests/regression-suite.md as a curated registry with registered tests, known gaps, and quarantined tests without removing entries unless explicitly approved.
  • Use Case: run after fixing a bug to confirm a regression test was added, or run before a release gate to ensure critical paths and closed bugs are guarded by tests.

Quick Start

Run /regression-suite update to scan closed bugs this sprint and propose or append missing regression tests 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 test coverage to GDD critical paths and identify missing regression tests?

Verifying bug fixes are test-covered requires scanning production/qa/bugs for closed bugs and detecting whether a corresponding regression test exists. If missing, suggested file paths for new regression tests are generated to prevent regressions from silently returning.

How do I maintain a regression test manifest without losing existing entries?

Maintaining a regression test manifest involves creating or updating tests/regression-suite.md as a curated registry of registered tests, known gaps, and quarantined tests. Existing entries are preserved unless explicitly approved for removal, ensuring historical coverage data is not lost.

Does this regression suite audit require a specific repository structure to run?

Yes, the regression suite audit requires a game repository containing a design/gdd directory, a tests folder, and production/qa/bugs. It also requires read access to repository files, glob and grep capabilities, and write access to append the tests/regression-suite.md manifest.

When should I run a regression test audit for closed bugs in my game repository?

You should run a regression test audit after fixing a bug, during sprint close, or before releases. Running the audit at these points confirms that newly closed bugs are guarded by regression tests and that GDD critical paths remain fully covered before code is shipped.

What is the best way to track missing regression tests for closed bugs?

The best way to track missing regression tests is to curate a tests/regression-suite.md manifest that registers known gaps and quarantined tests. Scanning closed bugs and mapping them against this registry identifies exactly where coverage drift occurs and suggests file paths for missing tests.