regression-suite

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

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill regression-suite-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regression-suite
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/regression-suite
Command: npx skills add https://github.com/MichaelSolati/mkai --skill regression-suite-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often face regression test suites that drift out of sync as new features launch, bugs are fixed, and GDD critical paths change, leading to missed regressions, recurring bugs, and blocked releases.

Core Features & Use Cases

  • Critical Path Coverage Mapping: Scans GDD acceptance criteria, formulas, and edge cases to identify gaps in existing test coverage.
  • Bug Regression Tracking: Verifies every closed bug has a corresponding regression test to prevent silent recurrence.
  • Coverage Drift Detection: Flags when new features or systems are added without corresponding test coverage, or when the suite becomes stale.
  • Use Case: For a game dev team, use this skill after fixing a player movement bug to confirm a regression test exists for that failure scenario, or run a full audit before a major release to catch all critical path coverage gaps.

Quick Start

Use the regression-suite skill to run a full audit of all GDD critical path test coverage before your next game release.

Frequently Asked Questions about regression-suite

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

FAQPage Schema
How do I verify regression test coverage for closed bug fixes in game development?

Verify regression test coverage for closed bug fixes by cross-referencing each resolved issue with a dedicated test case. This prevents silent bug recurrence by maintaining a curated manifest that tracks known failure scenarios and validates them during post-fix sprints.

What is coverage drift in game regression testing and how do I detect it?

Coverage drift in game regression testing occurs when new features launch without matching tests, causing suites to become stale. Detect coverage drift by flagging missing test coverage when systems are added or when existing tests no longer align with critical paths.

Can I map GDD acceptance criteria and edge cases to existing test coverage?

Map GDD acceptance criteria and edge cases to existing test coverage by scanning game design documents to identify gaps. This critical path coverage mapping highlights missing tests for formulas and edge cases before a major release gate check.

How do I run a full regression test audit before a game release?

Run a full regression test audit before a game release by scanning all GDD critical paths and closed bug fixes. This pre-release gate check identifies coverage gaps across acceptance criteria, formulas, and edge cases to prevent blocked releases.

Does this regression testing approach work for sprint close coverage audits?

This regression testing approach works for sprint close coverage audits by validating that newly implemented features and bug fixes have corresponding tests. It flags coverage drift and ensures closed bugs have regression tests to prevent silent recurrence.