regression-suite

Map automated tests to game design critical paths and fixed bugs.

47|12|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill regression-suite-nuoyanruoshui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/regression-suite
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill regression-suite-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents fixed bugs and critical gameplay paths from losing test coverage as the game evolves, keeping the regression suite aligned with releases and sprint changes.

Core Features & Use Cases

  • Regression Mapping: Map existing tests to GDD acceptance criteria, formulas, edge cases, and critical systems.
  • Bug Coverage Audits: Identify fixed bugs that lack tests capable of catching the original failure.
  • Coverage Drift Detection: Find newly completed stories or systems without corresponding regression coverage.
  • Suite Maintenance: Create or update tests/regression-suite.md while preserving existing registrations and clearly documenting gaps, quarantined tests, and release readiness.
  • Use Case: After fixing a save-system bug, run an update to verify that a regression test exists, register it in the suite, and flag any remaining coverage gap.

Quick Start

Use the regression-suite skill in audit mode to compare GDD critical paths, fixed bugs, and existing tests, then produce an updated coverage report.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I map automated test coverage to game design critical paths?

To map test coverage to game design critical paths, you need to compare GDD acceptance criteria against your test inventory. This process identifies which automated tests protect core gameplay formulas and edge cases, highlighting unprotected areas in your regression suite.

Why do fixed bugs lack regression test coverage as a game evolves?

Fixed bugs lose regression test coverage when new features or system revisions cause coverage drift, and tests are not updated to validate the original failure. A bug coverage audit identifies these gaps by comparing closed bug records against existing regression tests.

How do I verify bug fixes and detect coverage drift during sprint closeout?

You verify bug fixes and detect coverage drift by running an audit that compares newly completed stories and closed bug records against existing tests. This produces a coverage report flagging missing regression tests and release readiness gaps.

Do I need GDD files and closed bug records to perform a regression suite audit?

Yes, you need GDD files, test inventories, closed bug records, and the regression suite manifest to perform an audit. These inputs allow the tool to map test coverage accurately and update the suite while preserving existing registrations.

What is the best way to maintain a regression suite without losing existing test registrations?

The best way to maintain a regression suite is to update tests/regression-suite.md by mapping new coverage while preserving existing registrations. This approach clearly documents coverage gaps, quarantined tests, and release readiness without overwriting current data.