Testing & QA · Donchitos/Claude-Code-Game-Studios

Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.

Donchitos/Claude-Code-Game-Studios

Creates a blank playtest report template or converts raw playtest notes into structured findings sorted into design, balance, bug and polish items.

Donchitos/Claude-Code-Game-Studios

Produces a sprint QA plan that classifies stories as logic, integration, visual or UI and sets automated tests, manual checks and smoke scope for each.

Donchitos/Claude-Code-Game-Studios

Maps existing tests to a game's critical paths, finds fixed bugs that lack regression tests and flags coverage drift as new features arrive.

Donchitos/Claude-Code-Game-Studios

Generates the observation protocol and analysis harness for an extended play session that hunts slow memory leaks, performance drift and late-appearing bugs.

Donchitos/Claude-Code-Game-Studios

Reviews the quality of test files and evidence documents per story, grading each ADEQUATE, INCOMPLETE, MISSING or NOT ASSESSED rather than only checking they exist.

Donchitos/Claude-Code-Game-Studios

Finds flaky tests in CI logs by aggregating pass rates, explains likely causes and recommends whether to quarantine or fix each one.

Donchitos/Claude-Code-Game-Studios

Generates engine-specific test helper libraries with assertion utilities, factory functions and mocks, placed where the engine's test runner compiles them.

Donchitos/Claude-Code-Game-Studios

Critical-path smoke gate before QA hand-off — runs the automated suite.

Donchitos/Claude-Code-Game-Studios

Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.

Donchitos/Claude-Code-Game-Studios