bugfix
Skill157 starsChanged 32 days agoMITView on GitHub
Fixes bugs of any size from hotfixes to complex debugging sessions using root cause diagnosis and TDD. User-invoked entry point via /bugfix; not for autonomous or subagent use.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- 5uck1ess/devkittheir own version, first seen Nov 15, 2026
- akshaypimprikar/pragmatheir own version, first seen Nov 11, 2026
- isanchez-aguilar/relayrace-aitheir own version, first seen Nov 8, 2026
- icarloscornejo/doertheir own version, first seen Nov 7, 2026
- ClaireAll/skillstheir own version, first seen Nov 5, 2026
- bhoon716/skill-forgetheir own version, first seen Nov 2, 2026
Used with
Projects with it also use feature, spec and 7 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.
bradtraversySkillfeature
Manage current feature workflow - start, review, explain or complete
Also in 7 projects that use this
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 4 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 8 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 projects that use this
Microsoft AzureSkilldocs
Also in 3 projects that use this
MicrosoftSkillpr-review
Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.
Also in 3 projects that use this
- +1 more from getsentry
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- alibaba/MNN★ 17ksame name
- SparkDevNetwork/Rock★ 701same name
- oasm-platform/open-asm★ 277same name
- atelier-fashion/adlc-toolkit★ 174same name
- team-attention/hoyeon★ 173same name
- Snowflake-Labs/coco-skills★ 54same name
- mrveiss/AutoBot-AI★ 44same name
- dan-the-dev/xp-developer-skills★ 31same name
- ecodelearn/template-claude-code-open★ 25same name
- ConfabulousDev/confab-web★ 15same name
25 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 repository68 other files it gives its agents.
- github-pages/agents.mdAGENTS.md
- adrSkill
- agent-protocolsSkill
- angular-idiomsSkill
- api-documentationSkill
- auditSkill
- axum-idiomsSkill
- browser-automationSkill
- chaos-testingSkill
- ci-cdSkill
- cli-developmentSkill
- code-reviewSkill
- cpp-idiomsSkill
- csharp-idiomsSkill
- data-engineeringSkill
- debugging-protocolSkill
- django-idiomsSkill
- dotnet-idiomsSkill
- elixir-idiomsSkill
- embedded-systemsSkill
- feature-flagsSkill
- flutter-idiomsSkill
- frontend-designSkill
- git-commit-integritySkill
- go-idiomsSkill
- guardrailsSkill
- hono-idiomsSkill
- incident-responseSkill
- java-idiomsSkill
- javascript-idiomsSkill
- kotlin-idiomsSkill
- laravel-idiomsSkill
- logging-implementationSkill
- ml-engineeringSkill
- mobile-designSkill
- mobile-testingSkill
- nextjs-idiomsSkill
- parallel-dispatchSkill
- payment-integrationSkill
- perf-optimizationSkill
- perf-optimizeSkill
- php-idiomsSkill
- postgres-idiomsSkill
- python-idiomsSkill
- rails-idiomsSkill
- react-idiomsSkill
- refactoring-patternsSkill
- refactorSkill
- research-methodologySkill
- ruby-idiomsSkill
- rust-idiomsSkill
- security-auditSkill
- sequential-thinkingSkill
- spring-boot-idiomsSkill
- sql-idiomsSkill
- structured-specSkill
- supply-chain-securitySkill
- swift-idiomsSkill
- testability-patternsSkill
- test-e2eSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 5 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Before starting, you MUST:
- Very specific: line 30
Read rule-priority.md for conflict resolution
- Very specific: line 35
Set Mode: Use task_boundary to set mode to PLANNING
- Distinctive: line 39
If the cause is not immediately obvious, activate the Debugging Protocol skill
- Very specific: line 48
Set Mode: Use task_boundary to set mode to EXECUTION
- Distinctive: line 53
If the fix touches integration boundaries (database queries, API calls, external services), write or update integration tests
- Very specific: line 59
Set Mode: Use task_boundary to set mode to VERIFICATION
- Distinctive: line 61
Run the full validation suite: quality checks per idiom skill, all tests, build check
- Very specific: line 62
If the fix touched UI or user-facing flows, run E2E validation per browser-automation skill
- Distinctive: line 63
If all checks pass, commit with conventional format per @git-workflow-principles.md
- Very specific: line 64
Use commit type fix(<scope>): <description>
“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-Fix Skill
Entry-point guard: This is a user-invoked command skill (
/bugfix). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.
Purpose
Fix bugs of any size — from one-line hotfixes to multi-file debugging sessions — without the overhead of a full feature workflow.
When to Use
- Bug fixes (any size, any complexity)
- Hotfixes for production issues
- Addressing review findings from
/audit - Regression fixes after deployments
- Flaky test fixes
When NOT to Use
- New features (use
/workflow-solo) - Refactoring (use
/refactor) - Code quality audits (use
/audit)
Pre-Implementation Checklist
Before starting, you MUST:
- Scan
.agents/rules/directory for applicable rules - Read
rule-priority.mdfor conflict resolution
Phases
Phase 1: Diagnose
Set Mode: Use task_boundary to set mode to PLANNING
- Identify the bug or issue
- Locate the affected code — trace from symptoms to root cause
- If the cause is not immediately obvious, activate the Debugging Protocol skill
- Assess blast radius — which files, features, and tests are affected?
- Define the fix in
task.md
Skills to consider:
- Debugging Protocol — for non-obvious root causes, flaky tests, or multi-component bugs
- Sequential Thinking — when multiple hypotheses need systematic evaluation
Phase 2: Fix + Test (TDD)
Set Mode: Use task_boundary to set mode to EXECUTION
- Write a failing test that reproduces the bug
- Apply the fix to make the test pass
- Verify existing tests still pass
- If the fix touches integration boundaries (database queries, API calls, external services), write or update integration tests
- Follow applicable rules:
- Error Handling Principles @error-handling-principles.md
- Logging and Observability Mandate @logging-and-observability-mandate.md
Phase 3: Verify + Ship
Set Mode: Use task_boundary to set mode to VERIFICATION
- Run the full validation suite: quality checks per idiom skill, all tests, build check
- If the fix touched UI or user-facing flows, run E2E validation per
browser-automationskill - If all checks pass, commit with conventional format per @git-workflow-principles.md
- Use commit type
fix(<scope>): <description>
Completion Criteria
- Root cause identified and documented
- Bug reproduced with a test
- Fix applied and test passes
- Integration tests updated (if applicable)
- Full verification suite passes
- Committed with
fixtype
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.

