Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/bug-report
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.
Passed 21 of 24 test cases with the skill, and 8 of 24 without it.
and 14 more in the full report
14 fixed7 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
A verification request is triggered for bug 888. A search across 'production/qa/bugs/BUG-*.md' finds no files matching that number. What verdict must be returned and what statement is given?
| Checked | Without skill | With skill |
|---|---|---|
| Returns a verdict of BLOCKED | Missed | Passed |
| Reports that no bug BUG-888 exists in production/qa/bugs/ | Passed | Passed |
The instructions your model reads when the skill loads.
!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).
Determine the mode from the argument:
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 recordIf no argument is provided, ask the user for a bug description before proceeding.
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
test cases passed, vs 8 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.