regression-suite

Analyze bug fixes and GDD critical paths to map test coverage.

Updated May 16, 2026
One-click install
npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill regression-suite-seonghuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/SeongHuni/LightNShadowSurviver/tree/main/GameStudio/codex/skills/regression-suite
Command: npx skills add https://github.com/SeongHuni/LightNShadowSurviver --skill regression-suite-seonghuni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that every bug fix is accompanied by a test that would catch the original bug and keeps the regression suite current as the game evolves, flagging coverage drift from new features.

Core Features & Use Cases

  • Regression Test Management: Identifies fixed bugs without regression tests and flags coverage drift.
  • Critical Path Coverage: Maps test coverage to GDD critical paths.
  • Test Suite Maintenance: Maintains tests/regression-suite.md, ensuring the suite stays current.
  • Use Case: Run after implementing a bug fix or before a release gate to verify test coverage.

Quick Start

Run the regression suite with the 'update' mode to scan new bug fixes and check for regression test presence.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I ensure a bug fix includes a regression test in game development?

To ensure a bug fix includes a regression test, you can run the suite in update mode to scan recent fixes and flag any missing tests that would catch the original bug.

How do I map test coverage to GDD critical paths?

You can map test coverage to GDD critical paths by parsing the Game Design Document and analyzing existing tests to verify that essential gameplay routes remain covered.

What is the best way to maintain regression suite integrity before a release gate?

The best way to maintain regression suite integrity before a release gate is to audit test coverage, flag drift from new features, and update the tests/regression-suite.md file.

How do I detect test coverage drift after adding new game features?

To detect test coverage drift after adding new features, analyze the updated codebase against the existing regression suite to identify untested critical paths and missing tests.

Do I need bug tracking integration to manage regression tests?

Yes, bug tracking integration is required to analyze fixed bugs, verify regression test presence, and map test coverage to GDD critical paths effectively.

When should I run a regression suite audit for my game project?

You should run a regression suite audit after implementing a bug fix or before a release gate to verify that test coverage maps to GDD critical paths and prevents regressions.