What problem does it solve?
Unstructured, incomplete bug reports waste development and QA time by missing critical context like exact reproduction steps, severity ratings, and affected systems, leading to delayed fixes and misprioritized issues that impact game quality.
Core Features & Use Cases
- Structured Bug Report Generation: Create standardized bug reports from user descriptions with all required fields including severity, priority, reproduction steps, and technical context.
- Static Code Analysis: Scan game code files to identify potential bugs like null references, off-by-one errors, unhandled edge cases, and resource leaks before they reach players.
- Fix Verification & Closure: Verify that reported bug fixes actually resolve the issue by re-running reproduction steps and checking for regressions, then formally close bugs with closure records.
- Use Case: A QA tester can use this skill to turn a vague user report of "the car crashes when turning left on track 3" into a full bug report with exact steps to reproduce, S2 severity rating, and list of affected game systems, or a developer can run it on a new game mode script to catch potential bugs before release.
Quick Start
Share a description of the bug you encountered, or provide the path to a code file you want to scan for potential issues, to generate a structured bug report or code analysis.