regression-suite

Map GDD critical paths and closed bugs to existing test suites.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of coverage drift and silent regression bugs by mapping GDD critical paths to existing test suites and identifying gaps in your testing strategy.

Core Features & Use Cases

  • Coverage Mapping: Automatically audits GDD critical paths against existing unit and integration tests.
  • Bug Regression Tracking: Ensures every closed bug is backed by a regression test to prevent recurrence.
  • Release Readiness: Provides a clear status report on test coverage, helping you decide if the project is ready for a release gate.

Quick Start

Run the regression-suite skill with the audit argument to perform a full check of your current test coverage against the game design document.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I map game design document critical paths to existing test suites for regression coverage?

To map game design document critical paths to test suites, this skill audits your GDD systems-index against existing unit and integration test directories to identify coverage gaps and prevent regression bugs.

How do I ensure closed bug reports are backed by regression tests?

To ensure closed bug reports are backed by regression tests, this skill maps closed bugs to existing test file structures to verify that each bug fix maintains system stability and prevents recurrence.

What is the best way to automate test coverage gap analysis before a release gate?

Automating test coverage gap analysis before a release gate involves running an audit against GDD critical paths to generate a comprehensive coverage report and manifest updates for release readiness.

Does this regression testing tool require access to specific project directories to work?

Yes, this regression testing tool requires access to the GDD systems-index and your existing unit and integration test file structures to operate across directories and generate accurate coverage reports.

Why does test coverage drift cause silent regression bugs in my QA automation workflow?

Test coverage drift causes silent regression bugs because unmapped GDD critical paths lack corresponding test suites, allowing new features and bug fixes to destabilize the system without triggering test failures.

When should I not use automated regression suite audits for my testing strategy?

You should avoid automated regression suite audits if your project lacks a structured GDD systems-index or existing unit and integration test file structures, as the tool requires these inputs to map coverage gaps.