What problem does it solve?
Unstructured or vague bug descriptions slow down triage, cause flaky fixes, and leave QA without clear reproduction steps or context. This Skill converts informal reports or code observations into complete, reproducible bug reports with severity, priority, environment, and likely affected files to accelerate debugging and resolution.
Core Features & Use Cases
- Structured Bug Reports: Produces a full bug report template including summary, reproduction steps, environment, severity, likely root cause, and related files.
- Analyze Code for Bugs: Reads specified files to identify null references, off-by-one errors, race conditions, and other likely defects and drafts reports with recommended fixes.
- Verify & Close Workflows: Verifies fixes by re-checking code paths and running available tests, and appends closure records when verified.
- Use Case: During a playtest, convert a player's description of a crash into a reproducible bug report, locate the likely source files, verify a patch, and close the bug once tests pass.
Quick Start
Create a structured bug report from the description 'Player falls through floor when jumping' and propose reproduction steps.