regression-suite

Map test coverage to GDD critical paths and audit regression tests for bug fixes.

14|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill regression-suite-euraika-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/regression-suite
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill regression-suite-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lose regression coverage as the game evolves, leading to bugs re‑appearing after fixes or new features. Without a curated list of tests tied to critical design paths, release gates cannot reliably ensure stability.

Core Features & Use Cases

  • Coverage Mapping: Scans test inventory and GDD critical paths to determine which acceptance criteria, formulas, and edge cases have regression tests.
  • Bug Regression Audit: Verifies that each closed bug is guarded by an existing test, flagging missing regression tests.
  • Drift Detection: Identifies gaps introduced by new stories, systems, or GDD updates and highlights stale or quarantined tests.
  • Report & Manifest Generation: Produces a human‑readable status report and updates tests/regression-suite.md with a curated manifest.
  • Modes: Supports update, audit, and report commands for flexible integration into sprints or release pipelines.

Quick Start

Execute the regression suite in audit mode to evaluate test coverage and receive a detailed 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 regression test coverage to GDD critical paths?

Mapping regression test coverage to GDD critical paths requires scanning the test inventory and design documentation to verify which acceptance criteria and edge cases have existing tests. This Skill automates that mapping by cross-referencing test files against documented critical paths.

How do I ensure every bug fix has an associated regression test?

Ensuring bug fixes have regression tests involves auditing closed bug records and flagging any missing test coverage. This Skill performs a bug regression audit to verify each resolved issue is actively guarded by a corresponding test in the suite.

What is the best way to detect stale or quarantined tests during a sprint close?

Detecting stale tests during sprint close requires identifying coverage gaps introduced by new stories or design updates. This Skill identifies drift by highlighting quarantined tests and missing coverage relative to recent GDD updates.

Can I generate a regression suite manifest and status report from existing test files?

Generating a regression suite manifest involves reading test files and bug records to produce a curated list. This Skill updates the regression suite manifest and outputs a human-readable status report detailing current coverage and missing tests.

When should I run an audit versus a report for release gating?

Running an audit evaluates test coverage and flags missing regression tests, while running a report produces a human-readable status summary. Use audit mode to actively evaluate gaps before release gating, and report mode to review suite status.

Do I need GDD documentation to check regression test coverage?

Checking regression test coverage against critical design paths requires access to GDD documentation, test files, and bug records. The Skill needs these inputs to accurately map tests to acceptance criteria and audit bug fixes.