regression-suite

Map GDD critical paths and closed bugs to existing unit and integration tests.

72|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill regression-suite-striderza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/regression-suite
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill regression-suite-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents recurring bugs and coverage gaps by maintaining a curated regression suite aligned to GDD critical paths and recently fixed issues.

Core Features & Use Cases

  • Critical-path coverage mapping: Audits acceptance criteria against existing unit/integration tests and flags COVERED/PARTIAL/MISSING/EXEMPT items.
  • Fixed-bug regression validation: Detects whether each closed/fixed bug has a corresponding regression test and surfaces missing guards.
  • Coverage drift detection: Identifies when new features, stories, or revised GDD content outgrow the regression suite’s coverage.
  • Curated manifest maintenance: Creates/updates tests/regression-suite.md and keeps it accurate over time.

Quick Start

Run the regression-suite audit to produce a coverage and gap report, then update the regression-suite manifest if approved.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I map closed bugs to existing integration and unit tests for regression coverage?

Mapping closed bugs to existing tests involves scanning your filesystem for test files and GDD sources to validate whether fixed bugs have corresponding regression guards, then flagging any missing coverage. This Skill automates that detection process.

What is regression suite manifest maintenance and how does it prevent coverage drift?

Regression suite manifest maintenance is the process of updating a curated test list to match revised GDD critical paths. It detects coverage drift by auditing new features and stories against the existing suite, ensuring no acceptance criteria are left MISSING or PARTIAL.

How do I audit GDD critical paths against my current test coverage before a release gate?

Auditing GDD critical paths requires reading your GDD sources and scanning tests via filesystem discovery to compare acceptance criteria against existing guards. This Skill flags items as COVERED, PARTIAL, MISSING, or EXEMPT to produce a gap report for release gates.

When should I run a regression suite audit to validate bug fixes?

You should run a regression suite audit after bug fixes, sprint closes, or before release gates. This ensures newly fixed issues have corresponding regression tests and verifies that critical path coverage remains intact without unexpected drift.

Does this regression suite tool require any specific CI platforms or dependencies to function?

No specific CI platforms or dependencies are required. This Skill operates independently using filesystem discovery methods like read, Glob, and Grep to scan tests and GDD sources directly within your repository.

How do I update the regression-suite manifest after auditing critical paths and fixed bugs?

To update the regression-suite manifest, you run the audit to generate a coverage report, then approve the update mode. The Skill will write the curated results directly to `tests/regression-suite.md` after receiving your explicit approval.