fix · buiducnhat — Claude Code skill for debugging and installation
This skill investigates a reproducible bug, applies a focused correction, and checks the outcome. It hands off work when the cause or risk exceeds a small fix.
MIT 280 installs ★ 48 updated 2026-07-06
npx skills add buiducnhat/cobrew --skill fix -a claude-codeWhat fix does
The skill starts by clarifying the expected and actual behavior, reproduction steps, and available evidence such as logs or failed tests. It then reproduces the issue, traces the relevant code or data flow to a root cause, and makes a targeted change. An optional bug-report template helps gather missing details.
Checks proceed from the changed behavior to nearby regressions and relevant project checks. The task is complete only when the reported failure no longer reproduces and the expected result is confirmed. If investigation cannot establish a cause, or the fix crosses subsystems, requires migration, or carries broader risk, the skill stops implementation and directs the agent to brainstorm or write-plan.
For Claude Code, install it with npx skills add buiducnhat/cobrew --skill fix -a claude-code; the skill file goes at ~/.claude/skills/fix/SKILL.md. This workflow is deliberately limited to contained changes, so architectural work needs a planning step instead.
What it helps with
- trace a reproducible failure from logs to its root cause
- patch a test regression and verify the changed behavior
- compare observed behavior with the expected result
- halt a local fix when the work spans multiple subsystems
Example prompts for the agent
- Investigate this login failure: submitting the form raises an exception. Reproduce it from these steps and logs, then verify a focused fix.
- Find the cause of this failing regression test, make the smallest correction, and run nearby checks.
- Assess whether this bug is contained; if the fix crosses subsystems, stop and recommend a planning step.
How to install fix
1Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill fix -a claude-code2Manually: put the files in place
~/.claude/skills/fix/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fix/
1Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill fix -a codex2Manually: put the files in place
.agents/skills/fix/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill fix -a cursor2Manually: put the files in place
.cursor/skills/fix/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install buiducnhat/cobrew plugins/cobrew/skills/fix2Manually: put the files in place
.github/skills/fix/SKILL.md1Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill fix -a gemini-cli2Platform CLI
gemini skills install https://github.com/buiducnhat/cobrew --path plugins/cobrew/skills/fixManually: put the files in place
.devin/skills/fix/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add buiducnhat/cobrew --skill fix -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about fix
How do I install fix in Claude Code?
Run npx skills add buiducnhat/cobrew --skill fix -a claude-code. The skill file is placed at ~/.claude/skills/fix/SKILL.md.
What does the fix skill do?
It reproduces a concrete bug, traces its root cause, makes a targeted change, and verifies the result. Work that grows beyond a contained fix is handed off for planning.
When does fix escalate to brainstorm or write-plan?
It escalates when the root cause remains unclear, changes span subsystems, or the work calls for a migration or broad refactor. Broad regressions during verification also trigger a handoff.
Source text
SKILL.md · MIT
--- name: fix description: Diagnose and fix bugs with root-cause analysis and verification. Use when you have a concrete issue report, failing behavior, runtime error, or test regression that should be resolved safely. Stop and escalate to brainstorm when scope or risk grows. argument-hint: "[bug report or issue description]" license: MIT --- # Fix ## Scope Gate (Required Before Starting) Use this skill only when all conditions below are true: 1. **Concrete issue signal exists** - Clear failing behavior, error, or regression is identified - Enough evidence exists to begin diagnosis (logs, stack trace, failing test, or reproducible steps) 2. **Likely localized fix path** - Issue appears constrained to a small area - No expected cross-system redesign or migration 3. **Low-to-moderate architectural risk** - Fix can be made without foundational changes - No phased rollout/feature-flag strategy is expected 4. **Straightforward verification path** - Reproduction and post-fix checks can be run in practical scope - Success criteria can be validated directly If any condition fails, escalate to `brainstorm` or `write-plan`. ## Hard Stop Escalation Criteria Immediately stop and switch to planning if any of these occur: - Root cause remains unclear after focused investigation - Fix requires cross-cutting architectural or data-model changes - Scope expands into large refactor or multi-module migration - Security/compliance-sensitive behavior is involved - Verification reveals broad regressions requiring phased mitigation - Multiple fix attempts fail without converging on a root cause Escalation action: 1. Stop all implementation activities. 2. Output the exact message: "This fix exceeds safe single-pass debugging limits. Ask, Recommend `brainstorm` or `write-plan` first to define phased diagnosis, implementation, and risk controls." ## Workflow ### Step 1: Intake and Contextualize 1. Understand the reported bug and define explicit expected behavior. 2. Collect/confirm minimum bug report fields: - Title - Expected behavior - Actual behavior - Reproduction steps - Evidence (logs, trace, screenshot, failing test output) - Environment (branch/OS/runtime/version if relevant) - Impact/severity 3. Load only the project context relevant to the bug: - If `docs/SUMMARY.md` exists, read it first. - Load only task-relevant detail docs. - Prioritize `Code Standard` docs for implementation conventions. - If docs conflict with code or user intent, use the available input/question tool before broad changes. ### Step 2: Reproduce and Diagnose 1. Reproduce the issue consistently. 2. Locate the failure point (file/function/line range/subsystem). 3. Trace control/data flow to identify the **root cause**. 4. Form a fix hypothesis and confirm it explains observed behavior. Guidelines: - Read surrounding code, not only the failing line. - Prefer root-cause correction over symptom patching. - Add temporary diagnostics only when needed; remove them after use. ### Step 3: Decide Small vs Bigger Fix Classify the work before coding: #### Small fix (continue in this skill) Most are true: - Root cause is clear and validated - Change surface is narrow (typically a few files) - Regression risk is limited and testable quickly #### Bigger/risky fix (escalate to `brainstorm` or `write-plan`) Any are true: - Root cause is uncertain - Multiple subsystems must change together - Requires migration, rollout sequencing, or broad refactor - Risk cannot be reasonably controlled in a single pass If it is a bigger fix, follow **Hard Stop Escalation Criteria**. ### Step 4: Implement (Small Fix Path) 1. State a brief 1-3 bullet implementation plan. 2. Apply the smallest targeted change that resolves the root cause. 3. Keep scope strict; avoid unrelated refactors. 4. Add/update regression tests when applicable. ### Step 5: Verify Run validation in increasing scope: 1. Focused checks for the changed behavior/module 2. Nearby regression checks 3. Relevant project checks (lint/typecheck/tests/build) as needed Fix is complete only when: - Reproduction no longer fails - Expected behavior is confirmed - No critical regressions are introduced If verification indicates broader impact, escalate to `brainstorm` or `write-plan`. ### Step 6: Complete and Report Provide a concise completion report with: - **Root cause** - **What changed** - **Why this fix works** - **Verification performed and results** - **Residual risks / follow-ups** If behavior or documentation-relevant rules changed, update the minimal relevant docs. If architecture changed, this should have been escalated. ## Rules - Do not guess when key context is missing. - Always prioritize root-cause fixes. - Keep blast radius minimal. - Do not mark done without verification. - Escalate early when scope/risk exceeds this skill. ## Optional Bug Report Template Use when the report is incomplete: - Title: - Expected behavior: - Actual behavior: - Reproduction steps: - Error logs/stack trace: - Environment: - Impact/severity: - Additional context:
© buiducnhat · MIT · buiducnhat/cobrew
Similar skills
All skills for Testing and QA →fix by other authors comes first.