bug-report
Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.
HYClub · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add HYClub/deepseek-harness-game-studios --skill bug-reportAbout this skill
name: bug-report description: "Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity." argument-hint: "[description] | analyze [path-to-file] | verify [BUG-ID] | close [BUG-ID]" user-invocable: true allowed-tools: Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion, Bash(bash "*/.claude/skills/bug-report/../../hooks/yaml-helper.sh" resolve_config *) model: sonnet
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Phase 1: Parse Arguments
Determine the mode from the argument:
- No keyword → Description Mode: generate a structured bug report from the provided description
analyze [path]→ Analyze Mode: read the target file(s) and identify potential bugsverify [BUG-ID]→ Verify Mode: confirm a reported fix actually resolved the bugclose [BUG-ID]→ Close Mode: mark a verified bug as closed with resolution record
If no argument is provided, ask the user for a bug description before proceeding.
Phase 2A: Description Mode
-
Parse the description for key information: what broke, when, how to reproduce it, and what the expected behavior is.
-
Search the codebase for related files using Grep/Glob to add context (affected system, likely files).
-
Draft the bug report:
# Bug Report
## Summary
**Title**: [Concise, descriptive title]
**ID**: BUG-[NNNN]
**Severity**: [S1-Critical / S2-High / S3-Medium / S4-Low]
**Priority**: [P1-Fix this sprint / P2-Fix soon / P3-Backlog / P4-Won't fix]
**Status**: Open
**Reported**: [Date]
**Reporter**: [the reporter's name as the user gives it, else `—`; never an email address or account ID taken from the session]
## Classification
- **Category**: [Gameplay / UI / Audio / Visual / Performance / Crash / Network]
- **System**: [Which game system is affected — when the bug spans systems, the one whose code must change; the others go under Related systems]
- **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]
The Severity and Priority labels use /bug-triage's S and P numbers and
names, which it parses out of this file. P4-Won't fix is its P4 — Won't fix / Deferred (an accepted risk), not a wishlist. If you change either ladder, change
.claude/skills/bug-triage/SKILL.md too.
Phase 2B: Analyze Mode
-
Read the target file(s) specified in the argument.
-
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 using the template above, with the likely trigger scenario and recommended fix filled in.
Phase 2C: Verify Mode
Find the bug file by its number, here and in close mode: Glob
production/qa/bugs/BUG-*.md and take the file whose number matches [BUG-ID],
whatever its zero-padding — an older three-digit file with a slug is found by
its number too. If none
matches, stop: "No bug [BUG-ID] in production/qa/bugs/." Verdict: BLOCKED
— no such bug.
Read that file. Extract the reproduction steps and expected result.
- Re-run reproduction steps — use Grep/Glob to check whether the root cause code path still exists as described. If the fix removed or changed it, note the change.
- Run the related test — if the bug's system has a test file in the engine's test root (
tests/Godot,Assets/Tests/Unity,Source/<Module>/Private/Tests/Unreal —.claude/docs/directory-structure.md), run it via Bash withcommands.testfromproject.yaml, narrowed to the affected suite where the runner allows — never a runner line written from memory, which drops the flags the engine needs (gdUnit4 hangs without--remote-debug tcp://127.0.0.1:0) — and report pass/fail.commands.testunset → no test ran: name the unset key and go on to step 3. - Check for regression — grep the codebase for any new occurrence of the pattern that caused the bug.
- Manual verification — when no related test ran (none covers the bug — the usual case where
qa.levelwaives tests —commands.testis unset, or the run did not complete), or the bug's Category is Visual or UI, whose look no automated test checks, ask viaAskUserQuestion: "Did you play the reproduction steps in [bug file] on a build with the fix? Which build?" —[No longer occurs]/[Still occurs]/[Not played yet]. Record the answer and the build as the user gives them; a changed code path is never taken as their answer.
Produce a verification verdict:
- VERIFIED FIXED — the bug is gone by every check that applies: any related test ran and passed, and, where step 4