When invoked with a description:

Parse the description for key information.

Search the codebase for related files using Grep/Glob to add context.

Generate the bug report:

Bug Report

Summary

Title: [Concise, descriptive title] ID: BUG-[NNNN] Severity: [S1-Critical / S2-Major / S3-Minor / S4-Trivial] Priority: [P1-Immediate / P2-Next Sprint / P3-Backlog / P4-Wishlist] Status: Open Reported: [Date] Reporter: [Name]

Classification

• Category: [Gameplay / UI / Audio / Visual / Performance / Crash / Network]
• System: [Which game system is affected]
• Frequency: [Always / Often (>50%) / Sometimes (10-50%) / Rare (<10%)]
• Regression: [Yes/No/Unknown -- was this working before?]

Environment

• Build: [Version or commit hash]
• Platform: [OS, hardware if relevant]
• Scene/Level: [Where in the game]
• Game State: [Relevant state -- inventory, quest progress, etc.]

Reproduction Steps

Preconditions: [Required state before starting]

1. [Exact step 1]
2. [Exact step 2]
3. [Exact step 3]

Expected Result: [What should happen] Actual Result: [What actually happens]

Technical Context

• Likely affected files: [List of files based on codebase search]
• Related systems: [What other systems might be involved]
• Possible root cause: [If identifiable from the description]

Evidence

• Logs: [Relevant log output if available]
• Visual: [Description of visual evidence]

Related Issues

• [Links to related bugs or design documents]

Notes

[Any additional context or observations]

When invoked with analyze :

• Read the target file(s).

• Identify potential bugs: null references, off-by-one errors, race conditions, unhandled edge cases, resource leaks, incorrect state transitions.

• For each potential bug, generate a bug report with the likely trigger scenario and recommended fix.