Menü
Structured bug report creation with repro steps, expected/actual behavior, and severity classification.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Run a comprehensive health check on the repo. Verifies README counts match reality, promised files exist, no unresolved placeholders, wiki index is synced, toolchain configs are valid, and agent roster is accurate. Use after making structural changes or before publishing.
Begin a new Roblox game project or onboard to an existing one. Use when starting a fresh session with no context, or when the user says "let's start" or "new project".
Generate a 3D asset from a reference image using Blender MCP's image-to-3D AI (Hyper3D). Optimizes for Roblox and exports FBX.
Generate a 3D asset for Roblox using Blender MCP. Creates models from text descriptions via AI (Hyper3D/Hunyuan3D) or downloads from PolyHaven/Sketchfab, optimizes for Roblox constraints, and exports FBX.
Inspect the current Roblox Studio state via MCP. Verifies instance hierarchy, checks for common structural issues, and reports findings.
Capture a screenshot of the current Roblox Studio viewport and analyze it. Use for visual verification of UI, lighting, level layout, and general game appearance.
| name | bug-report |
| description | Structured bug report creation with repro steps, expected/actual behavior, and severity classification. |
Ask the user for:
Work with the user to find reliable repro steps:
Use .claude/docs/templates/bug-report-template.md as the base.
# BUG: [Short descriptive title]
**ID**: BUG-YYYY-MM-DD-NNN
**Severity**: [S0-S4]
**Device**: [Platform, resolution, network]
**Build**: [Version or git commit]
**Reported**: YYYY-MM-DD
**Status**: Open
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Evidence
- Screenshots: [paths or links]
- Video: [link if available]
- Console output: [paste relevant errors]
- Stack trace: [paste if available]
## Affected Systems
- [System 1]
- [System 2]
## Suspected Root Cause
[Any theories about where the bug lives]
## Workaround (if known)
[Anything the user can do to avoid it]
## Notes
[Anything else relevant]
Present the report to the user. On approval:
production/bugs/BUG-<date>-<NNN>.mdproduction/bugs/index.md if that exists