Skip to content
Get packs

Bug Report Writer

Turns a bug description or source file into a structured, triaged bug report with repro steps.

Source Download skill
Repository
Donchitos/Claude-Code-Game-Studios
Stars
32,965
Licence
MIT
Files
1 file

What it does

Once installed, the agent can take a rough description of a game bug and produce a structured report with severity, priority, reproduction steps, expected vs actual results, and likely affected files found by searching the codebase. It can also scan a source file for likely bugs such as null references or race conditions, and later check whether a reported fix actually resolved the bug, or mark it closed. Reports are saved as draft files under production/qa/bugs/ for a human to submit.

Great for

  • Game developers and QA leads on the Claude Code Game Studios setup who want consistent bug write-ups
  • Small teams that need severity and priority labels compatible with the bug-triage skill
  • Anyone who wants a first pass at spotting common code defects in a specific file

Skip it if

  • Projects outside the game-studio folder structure, since it expects paths like production/qa/bugs/ and a project.yaml config; results will be generic or the file lookups will fail
  • Filing issues directly: the skill is designed to write drafts only and never submits to trackers, so it will not help with automated submission
  • Treating analyze mode output as confirmed bugs: it reasons from reading code and can report false positives that need human checking

Try asking

  • “Write a bug report: the inventory duplicates items when I drop a stack onto a full hotbar after loading a save”
  • “Analyze src/combat/damage.gd for potential bugs”
  • “Verify BUG-0042 to check whether the fix really resolved it”
  • “Close BUG-0042 with a resolution record once it is verified”
Step-by-step guide: how to use Bug Report WriterInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    bug-report.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip bug-report.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip bug-report.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give concrete reproduction steps, build version and platform in your description so the report has fewer blanks to fill in
  • Set commands.test in project.yaml so verify mode can run real tests instead of relying on manual play
  • Review every draft before submitting it to your own tracker, especially root-cause guesses under Technical Context

What's inside

  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.