regression-suite

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill maps existing test coverage to the game's GDD critical paths, detects bugs that were fixed without accompanying regression tests, and prevents coverage drift as new features are added. It helps teams maintain a curated regression manifest so fixes do not silently reoccur and release gates can require trusted coverage.

Core Features & Use Cases

  • Audit critical paths by scanning design/gdd systems and matching acceptance criteria to unit and integration tests.
  • Validate bug fixes by locating closed bugs in production/qa/bugs and checking for corresponding regression tests, flagging gaps and suggesting test file names.
  • Detect coverage drift by comparing recent sprint stories, new systems, and file modification history against the last regression-suite update.
  • Generate and maintain a manifest at tests/regression-suite.md with a curated index of high-priority regression tests, quarantined tests, and known gaps; ask for confirmation before writing changes.
  • Modes: update (append new entries), audit (full rewrite and coverage scoring), and report (read-only status summary).

Quick Start

Run the regression-suite in update mode to scan closed bugs this sprint, map them to 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 test coverage to GDD critical paths in a game codebase?

Test coverage is mapped to GDD critical paths by scanning design/gdd systems and matching acceptance criteria to existing unit and integration tests, identifying missing or stale regression tests.

How do I ensure bug fixes have regression tests before a release gate?

Bug fixes are validated by locating closed bugs in production/qa/bugs and checking for corresponding regression tests, flagging gaps and suggesting test file names before release gates.

What is the best way to detect regression test coverage drift after new features are added?

Coverage drift is detected by comparing recent sprint stories, new systems, and file modification history against the last regression-suite manifest update to find missing tests.

How do I maintain a regression test manifest for a game project?

A regression manifest is maintained at tests/regression-suite.md by running update mode to append new entries, audit mode for full rewrites, or report mode for a read-only status summary.

Do I need a specific folder structure to audit regression tests for my game?

Yes, auditing requires a game codebase containing tests/ directories, design/gdd/ documentation, and production/qa/bugs/ records to correctly map coverage and validate fixes.

Why are closed bugs reoccurring despite having unit and integration tests?

Closed bugs reoccur when fixes lack accompanying regression tests; auditing closed bug records against existing test coverage flags these gaps to prevent silent regressions.