gds-test-review

Reviews game test suite quality, coverage gaps, and infrastructure to produce a prioritized report.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-test-review-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-test-review
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-test-review
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-test-review-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game test suites degrade over time through flaky tests, slow execution, and untested features, and teams lack a structured way to measure and fix this decay. This Skill audits an existing test suite and produces a prioritized review report. ## Core Features & Use Cases - Test Metrics Collection: Counts tests by type (unit, integration, play mode, performance), pass rates, durations, and identifies flaky, slow, and disabled tests. - Quality and Anti-Pattern Analysis: Evaluates determinism, isolation, speed, and readability, and detects anti-patterns like hard-coded waits, shared state, and assertion-free tests. - Coverage Gap and Infrastructure Review: Maps feature coverage against P0/P1 priorities and audits CI integration, fixtures, and maintenance burden. - Use Case: A QA lead on a Unity game project runs a monthly review to find that save/load has no P0 tests and three flaky tests block CI, then receives a sprint-ready action list. ## Quick Start Ask the AI to review the tests in this project and generate a test review report with coverage gaps and prioritized recommendations.

Frequently Asked Questions about gds-test-review

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

FAQPage Schema
How do I review test coverage for a game project?

Run a test review that maps each game feature against existing tests, classifies coverage by P0/P1 priority, and flags untested critical paths like save/load or core loop. The output is a coverage matrix with gaps prioritized by risk and player impact.

How to find and fix flaky tests in a test suite?

Flaky tests are identified by analyzing recent run history for inconsistent results. Common fixes include replacing hard-coded waits like Task.Delay with explicit condition waits, isolating shared test state, and adding proper synchronization.

Does this test review work with Unity, Unreal, and Godot?

Yes, the workflow supports a game_engine variable that can be set to unity, unreal, godot, or auto-detected. The review criteria apply across engines since they target general test quality practices rather than engine-specific APIs.

What test anti-patterns does the review detect?

The review detects hard-coded waits, shared static test state, tests of private implementation details, missing cleanup of instantiated objects, and assertion-free tests. Each finding is logged with severity, affected test count, and a recommended fix.

How often should a game test suite be reviewed?

The workflow recommends weekly quick checks of pass rates and flaky tests by QA, monthly full reviews of coverage and quality by a tech lead, and quarterly deep dives into infrastructure and strategy by the whole team.