regression-suite

Scan test inventories and flag gaps against GDD critical paths.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill regression-suite-packetalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/regression-suite
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill regression-suite-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Regression Suite keeps regression coverage aligned with the game's evolving features by curating a current list of tests that validate critical paths and guard against bug regressions.

Core Features & Use Cases

  • Maintains a living registry of regression tests mapped to tests in tests/unit, tests/integration, and tests/regression.
  • Audits coverage against GDD critical paths, bugs, and closed issues to surface gaps and drift.
  • Integrates with sprint plans to identify missing tests before releases and support decision-making.

Quick Start

Invoke the regression-suite to update, audit, or report on regression coverage for the current sprint.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I find missing regression tests for critical game paths?

To find missing regression tests, scan your test inventories and compare them against GDD critical paths. This process flags coverage gaps and stale entries, ensuring your automated tests align with the game's evolving features and sprint plans.

What is the best way to maintain automated regression coverage during a sprint?

Maintain automated regression coverage by auditing a living registry of tests against GDD critical paths and closed issues. This identifies missing tests before releases and supports decision-making aligned with your current sprint plan.

Can I audit test coverage across unit, integration, and regression directories?

Yes, you can audit test coverage by scanning tests in tests/unit, tests/integration, and tests/regression directories. The audit compares these inventories against critical paths to surface drift and gaps.

Does regression coverage tracking work with a manifest-only update flow?

Yes, regression coverage tracking supports a manifest-only update flow. This allows you to curate the current list of tests using audit and report modes without directly modifying the test codebase.

Why does regression test coverage drift away from the game design document?

Regression test coverage drifts because game features evolve continuously across sprints. Without scanning test inventories and comparing them against GDD critical paths, stale entries and untested paths accumulate over time.