regression-suite

Identify regression coverage gaps and compile a test manifest for critical game paths.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill regression-suite-naxoruto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/naxoruto/TE-limonchero-3d/tree/main/.claude/skills/regression-suite
Command: npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill regression-suite-naxoruto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures bug fixes are validated by regression tests and keeps the central regression registry up-to-date as the game evolves.

Core Features & Use Cases

  • Curates and maintains a manifest of tests located under tests/ that collectively cover GDD critical paths and known failure points.
  • Outputs the registry to tests/regression-suite.md and tracks last updates, gaps, and quarantined items.
  • Runs in update or audit mode to align test coverage with sprint work and release gates.

Quick Start

Run the regression-suite update after bug fixes or audit before a release to refresh the registry.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I track regression test coverage gaps for critical game paths?

To track regression test coverage gaps, this skill reads sprint plans and test inventories to identify missing tests and outputs a curated manifest guarding critical game paths.

What is the best way to maintain a regression suite after a bug fix or sprint closure?

To maintain a regression suite after bug fixes or sprint closures, run the update mode to refresh the test manifest and ensure all recent changes are validated against the registry.

How does regression coverage drift happen and how do I detect it?

Regression coverage drift happens when new features or bug fixes lack corresponding tests. Detect it by running an audit mode that compares the current test inventory against GDD changes.

Can I use this to align test coverage with GDD changes before a release?

Yes, you can align test coverage with GDD changes before a release by running an audit mode to surface missing tests and confirm required tests for critical paths.

What format does the regression suite registry use to track tests?

The regression suite registry uses a markdown file located at tests/regression-suite.md to track test manifests, last updates, coverage gaps, and quarantined items.

When should I run an audit instead of an update for my regression tests?

Run an audit before a release to detect coverage drift and surface missing tests, whereas run an update after bug fixes or sprint closures to refresh the registry with new tests.