bug-report

Creates structured bug reports with reproduction steps, severity assessment, and verification workflows.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill bug-report-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/bug-report
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill bug-report-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, actionable bug reports is tedious, and teams often file reports missing reproduction steps, severity ratings, or environment context, making bugs hard to triage and fix. ## Core Features & Use Cases - Structured Report Generation: Converts a plain-language bug description into a complete report with severity, priority, environment, reproduction steps, and technical context. - Code Analysis Mode: Scans target files to detect potential bugs such as null references, off-by-one errors, race conditions, and resource leaks, then drafts a report for each finding. - Verify and Close Lifecycle: Re-runs reproduction steps and related tests to confirm a fix works, then writes a closure record so bugs are never closed without verification. - Use Case: A QA tester describes a crash that happens when opening the inventory screen; the Skill searches the codebase for related files, drafts a full report with reproduction steps, and saves it to production/qa/bugs/ for triage. ## Quick Start Use the bug-report skill to create a structured bug report for the crash that occurs when opening the inventory screen.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I write a good bug report with reproduction steps?

Provide a plain description of what broke, when, and the expected behavior. The Skill parses it, searches the codebase for affected files, and drafts a report with severity, environment, exact reproduction steps, and expected versus actual results.

How to find potential bugs in source code automatically?

Run the Skill in analyze mode with a target file path. It reads the code and flags null references, off-by-one errors, race conditions, unhandled edge cases, resource leaks, and incorrect state transitions, generating a report per finding.

Can I verify a bug fix before closing the ticket?

Yes, verify mode re-runs the reproduction steps against the current code, executes related tests if they exist, and greps for regressions. It returns VERIFIED FIXED, STILL PRESENT, or CANNOT VERIFY before any status change.

What severity levels does the bug report template use?

Reports use four severity levels from S1-Critical to S4-Trivial, plus priority levels P1 through P4. Classification also covers category, affected system, frequency, and whether the bug is a regression.

Where are the generated bug reports saved?

Reports are written to production/qa/bugs/BUG-[NNNN].md after you approve the write. The Skill asks for confirmation before saving and suggests running bug triage or hotfix workflows afterward.