regression-suite

Map GDD critical paths and closed bugs to existing unit and integration test coverage.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill regression-suite-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/regression-suite
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill regression-suite-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents game-breaking bugs from reappearing by ensuring every important fix is guarded by regression tests and that the suite stays aligned with your design.

Core Features & Use Cases

  • Map critical paths to tests: Audit GDD acceptance criteria against existing unit and integration tests to spot missing or partial coverage.
  • Link closed bugs to regression coverage: Detect whether each fixed bug has a corresponding test that would catch the original failure scenario again.
  • Maintain a suite manifest: Update or report tests/regression-suite.md so release gates know what must pass and what is at risk.

Quick Start

Run /regression-suite audit to identify critical-path gaps and missing regression tests before your next release gate.

Frequently Asked Questions about regression-suite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map GDD critical paths to existing test coverage?

Regression testing prevents recurring game bugs by linking closed bugs and GDD critical paths to specific unit and integration tests. This ensures every important fix is guarded against recurrence and maintains suite alignment with your design.

How do I link closed bugs to regression tests in game development?

Link closed bugs to regression testing by checking whether each fixed bug has a corresponding test that catches the original failure scenario. This ensures your suite manifest tracks which fixes are actively protected against recurrence.

Do I need a specific test directory structure for regression testing?

Regression testing requires a tests directory to scan for inventory and a design file mapping critical paths. It reads existing unit and integration tests to audit coverage against design acceptance criteria before writing updates.

What's the best way to prevent test coverage drift when adding new game features?

Prevent test coverage drift by auditing GDD critical paths against existing unit and integration tests. This regression testing approach spots missing coverage and updates the manifest so release gates know exactly what must pass.

When should I run a regression suite audit before a game release?

Run a regression suite audit before release gates to identify critical-path gaps and missing regression tests. This verifies that closed bugs remain protected and new features have not caused test coverage drift.