mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 04:51:46 +00:00
ad540fe75d
48 coordinated Claude Code subagents for indie game development: - 3 leadership agents (creative-director, technical-director, producer) - 10 department leads (game-designer, lead-programmer, art-director, etc.) - 23 specialist agents (gameplay, engine, AI, networking, UI, tools, etc.) - 12 engine-specific agents (Godot, Unity, Unreal with sub-specialists) Infrastructure: - 34 skills (slash commands) for workflows, reviews, and team orchestration - 8 hooks for commit validation, asset checks, session management - 11 path-scoped rules enforcing domain-specific standards - 28 templates for design docs, reports, and collaborative protocols Key features: - User-driven collaboration protocol (Question → Options → Decision → Draft → Approval) - Engine version awareness with knowledge-gap detection (Godot 4.6 pinned) - Phase gate system for development milestone validation - CLAUDE.md kept under 80 lines with extracted doc imports Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
76 lines
2.3 KiB
Markdown
76 lines
2.3 KiB
Markdown
---
|
|
name: bug-report
|
|
description: "Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context."
|
|
argument-hint: "[description]
|
|
/bug-report analyze [path-to-file]"
|
|
user-invocable: true
|
|
allowed-tools: Read, Glob, Grep, Write
|
|
---
|
|
|
|
When invoked with a description:
|
|
|
|
1. **Parse the description** for key information.
|
|
|
|
2. **Search the codebase** for related files using Grep/Glob to add context.
|
|
|
|
3. **Generate the bug report**:
|
|
|
|
```markdown
|
|
# 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`:
|
|
|
|
1. **Read the target file(s)**.
|
|
2. **Identify potential bugs**: null references, off-by-one errors, race
|
|
conditions, unhandled edge cases, resource leaks, incorrect state
|
|
transitions.
|
|
3. **For each potential bug**, generate a bug report with the likely trigger
|
|
scenario and recommended fix.
|