skills.rest
johnatas-henrique
johnatas-henriqueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

regression-suite

Map test coverage to game design document critical paths and closed bug fixes.

Updated Jul 16, 2026
Search Tags:#game development#test coverage#regression testing#bug fixes#gdd alignment#test suite maintenance#coverage drift
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill regression-suite-johnatas-henrique
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/regression-suite
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill regression-suite-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common issue of regression test suites falling out of sync with game updates, which leads to previously fixed bugs reappearing and untested critical paths making it to release without verification.

Core Features & Use Cases

  • Critical Path Coverage Mapping: Scans game design document (GDD) acceptance criteria to identify untested core functionality and flag high-priority coverage gaps for formulas and state machines.
  • Bug Regression Test Tracking: Identifies closed bug fixes that lack corresponding regression tests, preventing silent recurrence of issues in future sprints.
  • Coverage Drift Detection: Flags when new features or systems are added without corresponding test coverage, or when the regression suite has not been updated for multiple sprints.
  • Use Case: For a 90s F1-style racing game like Overdrive, after fixing a bug where car acceleration glitches on wet tracks, this skill will flag if no regression test exists for that scenario, add it to the suite manifest, and ensure all GDD-defined critical racing mechanics are covered before a release gate.

Quick Start

Invoke the regression-suite skill in update mode after implementing a bug fix to verify a regression test exists and update the test suite manifest.

Frequently Asked Questions about regression-suite

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

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

To map test coverage to game design document critical paths, scan GDD acceptance criteria to identify untested core functionality. This process flags high-priority coverage gaps for formulas and state machines, generating gap reports to ensure critical game mechanics are guarded against regressions.

How do I track closed bug fixes that are missing regression tests?▼

Track closed bug fixes lacking regression tests by auditing closed issues against the test suite manifest. Identifying these missing tests prevents silent recurrence of issues in future sprints, ensuring every resolved bug has a corresponding verification check before release gates.

What is coverage drift detection in regression testing?▼

Coverage drift detection in regression testing identifies when new features or systems are added without corresponding test coverage, or when the test suite has not been updated for multiple sprints. It flags these gaps to maintain synchronization between game updates and regression tests.

Can I use this approach to audit test coverage before a game release gate?▼

Yes, you can audit test coverage before a game release gate by mapping critical paths and closed bug fixes to existing tests. This generates a curated regression suite manifest and gap reports, ensuring all high-priority game functionality is verified and guarded against regressions.

How do I update a regression suite after fixing a game bug?▼

Update a regression suite after fixing a game bug by invoking the skill in update mode to verify a regression test exists for the scenario. If missing, it adds the test to the suite manifest, preventing the fixed bug from silently reappearing in future updates.

Why do previously fixed bugs reappear in game development sprints?▼

Previously fixed bugs reappear when regression test suites fall out of sync with game updates and lack corresponding regression tests. Tracking closed bug fixes and updating the suite manifest after each fix prevents silent recurrence of these issues across development sprints.

Related Skills

Explore More Software Engineering Skills→
MichaelSolatiMichaelSolati

regression-suite

Align game regression tests with GDD critical paths and closed bug fixes.

Community
Advanced
rakhnianskii9rakhnianskii9

regression-suite

Generate a regression test manifest and status reports from sprint plans and test inventories.

Community
Advanced
adityaarsharmaadityaarsharma
2

orbit-qa-regression-pack

Manage regression test suites with Playwright and CI pipelines.

Community
Advanced
levnikolaevichlevnikolaevich
534

ln-632-test-e2e-priority-auditor

Audit E2E test coverage for critical paths and core journeys.

Community
Advanced