bugfix
Skill2 starsChanged 6 months agoMITView on GitHub
End-to-end bugfix workflow — analyze environment (local Docker or cloud production), collect evidence, prepare bug report, plan fix, apply appropriate engineer role, implement and verify the fix.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- 5uck1ess/devkittheir own version, first seen Nov 15, 2026
- ClaireAll/skillstheir own version, first seen Nov 13, 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
- bhoon716/skill-forgetheir own version, first seen Nov 2, 2026
Used with
Projects with it also use feature, refactor and 6 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
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 6 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
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
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
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
- irahardianto/awesome-agv★ 157same 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
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 repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- social-media-managerSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
28 rules. 0 are common, 24 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
24
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
If the user provides partial information, extract what you can and fill gaps during analysis.
- Distinctive: line 43
Run the follow-up skill. It will:
- Distinctive: line 84
Timeline: When did it start? What changed?
- Distinctive: line 90
Use the applied role's debugging methodology to trace the bug:
- Distinctive: line 91
Read error stack traces to identify the failing code path
- Distinctive: line 92
Search codebase for related functions, error handlers, and data flows
- Distinctive: line 93
Check recent changes (git log -n 20 --oneline) for potential regressions
- Distinctive: line 138
Wait for user confirmation before proceeding to fix.
- Distinctive: line 142
Create an ordered fix plan following the applied role's guidelines:
- Distinctive: line 171
Wait for user approval before implementing.
- Distinctive: line 180
Verify the code compiles/parses without errors
- Distinctive: line 185
Run the full test suite to catch regressions
- Distinctive: line 191
Follow existing code patterns and conventions
- Distinctive: line 192
No new warnings or linter errors — and fix pre-existing ones in the affected files if trivial
- Distinctive: line 193
Do not defer fixes to "follow-up" tasks — complete the fix in this changeset
- Distinctive: line 194
Do not increase tech debt — if you touch it, leave it better than you found it
- Distinctive: line 195
If the fix is more complex than expected — stop and discuss with the user
- Very specific: line 196
If you need more information about the environment, run specialized follow-up skills (analyze-local skill or analyze-prod skill) to collect …
- Distinctive: line 200
Before declaring the bug fixed, perform a thorough self-review.
- Distinctive: line 211
If the self-review reveals any remaining issues — fix them before proceeding.
- Distinctive: line 215
Verify the bug is resolved in the appropriate environment:
- Distinctive: line 218
Run the reproduction steps — confirm the bug no longer occurs
- Distinctive: line 219
Run the full test suite — all tests pass (new + existing)
- Very specific: line 220
If Docker-based: rebuild and verify with analyze-local skill (optional)
- Very specific: line 221
If you need more data, run specialized follow-up skills for analyze-local skill to collect environment state
- Distinctive: line 224
Verify the fix locally first
- Very specific: line 226
After deploy: re-run relevant checks from analyze-prod skill to confirm resolution
- Distinctive: line 239
If any check fails — fix and re-verify.
“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
Bugfix
End-to-end workflow for investigating, diagnosing, and fixing bugs. Orchestrates environment analysis (analyze-local skill or analyze-prod skill), evidence collection, bug report preparation, fix planning, and implementation by the appropriate engineering role.
1. Receive Bug Report
Gather the bug description from the user:
- What is the expected behavior?
- What is the actual behavior? (error message, wrong output, crash, performance issue)
- Steps to reproduce (if known)
- Environment: local (Docker) or production (cloud K8s)?
- When did it start? (after deploy, config change, or unknown)
- Severity: P1 (outage), P2 (degraded), P3 (minor), P4 (cosmetic)
If the user provides partial information, extract what you can and fill gaps during analysis. For P1/P2 — skip detailed intake and proceed immediately to Step 2.
2. Analyze Environment
Based on the environment, delegate to the appropriate analysis follow-up skill:
| Environment | follow-up skill | When to use |
| Local Docker / Docker Compose | analyze-local skill | Bug observed in local dev environment |
| Cloud production (GKE/AKS/EKS, managed DB) | analyze-prod skill | Bug observed in production or staging |
| Code-only (no infra) | Skip to Step 3 | Bug is in application logic, no environment analysis needed |
Run the follow-up skill. It will:
- Apply the appropriate diagnostic role (
sre-engineerrole ordevops-engineerrole) - Collect environment snapshot (container/pod status, logs, metrics, networking)
- Identify infrastructure-level issues
- Present diagnosis
If the follow-up skill resolves the issue (e.g., container restart, config fix) — skip to Step 8.
If the root cause is in application code — continue to Step 3 with the collected evidence.
3. Detect Stack and Apply Engineer Role
Determine the affected service's tech stack and apply the appropriate engineering role:
- Read project's
AGENTS.md— tech stack declaration - Scan project files —
package.json,pom.xml,requirements.txt,go.mod, etc. - Check evidence from Step 2 — which service's logs show the error? What language is the stack trace in?
Role assignment:
| Stack Signal | Role |
Next.js, React, TypeScript, .tsx files | frontend-engineer role |
Spring Boot, Java, .java files | java-engineer role |
FastAPI, Python, .py files | python-engineer role |
| Terraform, Dockerfile, Helm, CI/CD | devops-engineer role |
| ML model, training pipeline, inference | ml-engineer role |
| Multiple stacks affected | Apply all relevant roles |
| Unknown / general | software-engineer role |
Announce the applied role(s) to the user.
4. Collect Evidence
Gather all evidence into a structured collection. Combine data from Step 2 (environment analysis) with code-level investigation:
<evidence_checklist>
- Error output: Full error message, stack trace, exit code
- Logs: Relevant log entries (timestamped) from the affected service
- Reproduction: Can you reproduce locally? Consistent or intermittent?
- Scope: Which endpoints / features / components are affected?
- Timeline: When did it start? What changed? (recent commits, deploys, config)
- Data: Specific inputs that trigger the bug (request payload, user ID, dataset)
- Metrics (if from prod): Error rate, latency change, affected user count
- Related code: Files, functions, lines most likely involved </evidence_checklist>
Use the applied role's debugging methodology to trace the bug:
- Read error stack traces to identify the failing code path
- Search codebase for related functions, error handlers, and data flows
- Check recent changes (
git log -n 20 --oneline) for potential regressions - Identify the minimal reproduction case
5. Prepare Bug Report
Compile findings into a structured bug report. Present to the user for review:
## Bug Report
### Summary
[One sentence: what is broken]
### Severity: [P1 | P2 | P3 | P4]
### Environment
- **Type**: [local | production]
- **Service**: [name]
- **Stack**: [detected] | **Role**: [applied]
### Expected Behavior
[What should happen]
### Actual Behavior
[What actually happens — include error messages]
### Steps to Reproduce
1. [step]
2. [step]
3. [observed error]
### Evidence
- **Stack trace**: [snippet or reference]
- **Logs**: [relevant entries]
- **Metrics**: [if applicable]
- **Affected code**: [file:line references]
### Root Cause Analysis
[Technical explanation of why the bug occurs]
### Affected Components
- [file/module 1] — [how it's affected]
- [file/module 2] — [how it's affected]Wait for user confirmation before proceeding to fix.
6. Plan the Fix
Create an ordered fix plan following the applied role's guidelines:
- Root cause fix — address the actual cause, not symptoms
- Complete fix — fix everything described in the bug report. Do not leave cosmetic issues, lint warnings, or minor problems unfixed. Do not create follow-up tickets for things you can fix now
- Regression test — test that would have caught this bug
- Related fixes — any adjacent issues discovered during investigation. Fix them in the same changeset — do not increase tech debt
Present the plan:
## Fix Plan
### Root Cause
[What caused the bug — one sentence]
### Changes
1. [file] — [what to change and why]
2. [file] — [what to change and why]
...
### Tests
1. [test file] — [test that reproduces and verifies the fix]
2. [test file] — [regression test for edge cases]
### Risk Assessment
- **Blast radius**: [which features could be affected by this change]
- **Rollback**: [how to revert if the fix causes issues]Wait for user approval before implementing.
7. Implement the Fix
Execute the approved plan step by step.
For each change:
- State what you are about to do (file, change summary)
- Implement the fix following the applied role's code quality standards
- Verify the code compiles/parses without errors
Then write tests:
- Regression test: Reproduces the original bug — must fail without fix, pass with fix
- Edge case tests: Cover related scenarios discovered during investigation
- Run the full test suite to catch regressions
Rules:
- Fix the root cause, not the symptom
- Fix EVERYTHING reported in the bug — do not leave non-blocking or cosmetic issues unfixed
- Fix all lint errors, style violations, and warnings introduced or exposed by the change
- Follow existing code patterns and conventions
- No new warnings or linter errors — and fix pre-existing ones in the affected files if trivial
- Do not defer fixes to "follow-up" tasks — complete the fix in this changeset
- Do not increase tech debt — if you touch it, leave it better than you found it
- If the fix is more complex than expected — stop and discuss with the user
- If you need more information about the environment, run specialized follow-up skills (
analyze-localskill oranalyze-prodskill) to collect it
8. Self-Review the Fix
Before declaring the bug fixed, perform a thorough self-review. Do NOT skip this step.
Code review checklist:
- Re-read every changed file diff — verify correctness and completeness
- Every item from the bug report or user description is addressed — nothing left unfixed
- No cosmetic issues, lint warnings, or style violations remain in changed files
- No TODO, FIXME, or "will fix later" comments introduced
- No tech debt created — the code is clean and production-ready
- Run linter on all changed files — zero warnings
- Run formatter on all changed files — zero diffs
If the self-review reveals any remaining issues — fix them before proceeding. Do not declare the bug fixed with known remaining problems.
9. Verify the Fix
Verify the bug is resolved in the appropriate environment:
For local bugs:
- Run the reproduction steps — confirm the bug no longer occurs
- Run the full test suite — all tests pass (new + existing)
- If Docker-based: rebuild and verify with
analyze-localskill (optional) - If you need more data, run specialized follow-up skills for
analyze-localskill to collect environment state
For production bugs:
- Verify the fix locally first
- Deploy through normal CI/CD pipeline (do NOT hotfix production directly)
- After deploy: re-run relevant checks from
analyze-prodskill to confirm resolution - Monitor error rates and SLIs for regression
Verification checklist:
- Original bug no longer reproduces
- ALL items from the bug report are fixed — not just the primary symptom
- Regression test passes
- Full test suite passes (no new failures)
- Linter passes with zero warnings on changed files
- No unrelated files modified
- Code follows project conventions and role guidelines
- No deferred work — everything is done in this changeset
If any check fails — fix and re-verify. Do NOT declare the bug fixed until every checkbox passes.
10. Summary
Present the completed bugfix:
- Bug: one-sentence summary
- Severity: P1–P4
- Environment: local / production
- Role(s) applied: which roles were used
- Root cause: technical explanation
- Fix: what was changed (files, brief description)
- Tests added: count and description
- Self-review: passed — all items verified
- Verification: how it was confirmed fixed
- Remaining issues: NONE (if any remain, go back and fix them before reporting)
- Prevention: recommendations to avoid similar bugs (e.g., add validation, improve error handling, add monitoring)
Integration
- follow-up skills:
analyze-localskill,analyze-prodskill (environment diagnostics — launch as specialized skills when more data is needed) - Follow-up:
run-testsskill (verify fix),pre-commitskill (quality gate),create-prskill (submit fix) - Skills:
code-reviewskill (review fix),test-strategyskill (test strategy),worktree-isolationskill (branch isolation)
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.

