bug-report
Skill9 starsChanged 7 months agoMITView on GitHub
Structured bug report creation with repro steps, expected/actual behavior, and severity classification.
34 other projects use a version of this.
Adopted by
Most recently taken up by
- MohamedRamadanSalah/claude-qa-toolkittheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- alexpalexpinne/qa-toolkittheir own version, first seen Nov 8, 2026
- craigcossairt/trellistheir own version, first seen Nov 6, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
Used with
Projects with it also use setup-engine, team-audio and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 13 projects that use this
lilangMaxSkillasset-spec
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Also in 10 projects that use this
lilangMaxSkillcreate-control-manifest
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Also in 10 projects that use this
- +3 more from CoralGame
- +4 more from lilangMax
Other versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- pipecat-ai/gradient-bang★ 420same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- oasm-platform/open-asm★ 277same name
- striderZA/OpenCodeGameStudios★ 124same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- composio-community/support-skills★ 18same name
- dawn840705/codex-code-studios★ 17same name
24 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Ask the user for:
- Distinctive: line 20
Frequency: Always / sometimes / once?
- Distinctive: line 25
Start from a known state (e.g., fresh login)
- Very specific: line 37
Use .claude/docs/templates/bug-report-template.md as the base.
- Very specific: line 83
Add to production/bugs/index.md if that exists
“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/bug-report — Bug Report Creation
Delegate to: qa-tester (with qa-lead for triage)
Steps
1. Gather Information
Ask the user for:
- Short description: One sentence summary
- What happened: What did you observe?
- What should have happened: Expected behavior
- When: Did this just start or has it been happening?
- Where: Which system/feature is affected?
- Device: Platform (mobile/PC/console), screen size, network
- Frequency: Always / sometimes / once?
- Impact: How many players affected? Data loss risk?
2. Reproduce (if possible)
Work with the user to find reliable repro steps:
- Start from a known state (e.g., fresh login)
- List each action taken
- Note the exact point where behavior diverges from expected
3. Classify Severity
- S0 — Critical: Data loss, crashes, security exploits, can't play
- S1 — Major: Feature broken for many users, major visual/UX issues
- S2 — Normal: Feature works but with noticeable problems
- S3 — Minor: Small glitches, edge cases, polish items
- S4 — Cosmetic: Typos, minor style issues
4. Generate Bug Report
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]5. Save and Triage
Present the report to the user. On approval:
- Save to
production/bugs/BUG-<date>-<NNN>.md - Add to
production/bugs/index.mdif that exists - For S0/S1: Immediately escalate to qa-lead + producer
- Delegate investigation to the appropriate specialist based on affected system
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

