regression-suite

Map tests to GDD critical paths and flag coverage drift.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LordKuper/agentic-game-studio --skill regression-suite-lordkuper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/regression-suite
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill regression-suite-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams maintain a reliable regression suite by aligning existing tests with GDD critical paths, flagging coverage drift, and surfacing gaps before release gates.

Core Features & Use Cases

  • Mapping: Associate tests under tests/unit and tests/integration with GDD critical paths to ensure coverage for core systems.
  • Audit & Drift Detection: Scan design/gdd files and sprint plans to identify missing tests and drift since the last update.
  • Manifest Generation: Produce a regression-suite manifest with recommended tests and drift indicators for sprint planning and QA gates.
  • Use Case: After a bug fix, verify there is a regression test, and before a release, confirm the suite covers all critical paths.

Quick Start

Run the regression-suite audit to identify coverage gaps and generate the manifest.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I map existing unit and integration tests to GDD critical paths?

Regression coverage drift is identified by scanning design/gdd files and sprint plans to compare current test inventories against the last known state, flagging missing tests and coverage gaps for core systems.

What is the best way to generate a regression suite manifest for sprint planning?

Run a regression suite audit after a bug fix to verify a corresponding regression test exists, scan tests/unit and tests/integration against GDD critical paths, and surface any coverage gaps before release.

How do I confirm regression coverage for all critical paths before a release gate?

Confirm regression coverage before a release by running an audit that maps tests under tests/unit and tests/integration to GDD critical paths, ensuring all core systems are covered and drift indicators are resolved.

Why does regression coverage drift occur during bug fixes and sprint reviews?

Regression coverage drift occurs when test inventories under tests/unit and tests/integration fall out of sync with GDD critical paths and sprint plans, leaving core systems without adequate test coverage over time.