skills.rest
iJosueeh
iJosueehCOMMUNITY
Explore all skills by this author →
GitHub

bug-fixer

Diagnose root causes of bugs through a four-stage systematic debugging process and apply minimal fixes.

Updated Jun 29, 2026
Search Tags:#debugging#root cause analysis#bug fixing#stack trace#regression testing#error diagnosis#systematic troubleshooting
One-click install
npx skills add https://github.com/iJosueeh/amauta --skill bug-fixer-ijosueeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-fixer
Source: https://github.com/iJosueeh/amauta/tree/main/.opencode/skills/bug-fixer
Command: npx skills add https://github.com/iJosueeh/amauta --skill bug-fixer-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a feature breaks, a compile error appears, or a runtime exception surfaces, this Skill replaces guesswork with a structured debugging loop that locates the actual root cause before any code is changed, then verifies the fix with evidence. ## Core Features & Use Cases - Four-Stage Debugging Process: Collect evidence, analyze patterns, verify hypotheses, then implement a surgical fix — no stage skipping allowed. - Diagnostic Checklists: CoT diagnostic checklist, dimension checklist, anti-rationalization rules, and a three-layer diagnostic model (symptom, design flaw, principle violation) prevent symptom-only patches. - Regression Protection: Every fix requires compile verification, reproduction verification, regression verification, and a test that would have caught the bug. - Use Case: A user reports "login fails with TypeError: Cannot read property 'id' of undefined". The Skill reproduces the bug, traces the call chain to a stale session reference, applies a one-line fix, adds a regression test, and reports the root cause with verification evidence. ## Quick Start Describe the bug, error message, or unexpected behavior you are seeing and ask the agent to run the bug-fixer workflow to find the root cause and fix it.

Frequently Asked Questions about bug-fixer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a runtime error systematically instead of guessing?▼

Follow a four-stage process: collect the full error message, stack trace, and reproduction steps first; analyze patterns against working code; form and test hypotheses one at a time; then apply a minimal fix. Never change code before the bug reproduces reliably.

How to find the root cause of a bug instead of fixing symptoms?▼

Trace the data flow from the trigger point to where the error surfaces, and read the stack trace from the root call upward to the first line of user code. Avoid wrapping errors in try-catch, which hides the cause rather than fixing it.

Can this Skill handle bugs found during code review?▼

Yes. It accepts failure items passed from a code-review report when the confidence is at least 0.6, then runs the same debugging workflow on each item. After fixing, the main agent re-dispatches code review to verify.

When should I not use a systematic debugging workflow?▼

Do not use it for feature requests, new functionality, code style issues without runtime errors, or general performance optimization. Those belong to development or code-review workflows rather than bug fixing.

What happens if the same bug keeps failing after multiple fixes?▼

The workflow enforces a three-strikes rule: after three failed fix attempts, it stops and re-examines the problem level, since repeated failure usually means the wrong layer is being debugged. The retry-gate escalates instead of looping.

Related Skills

Explore More Software Engineering Skills→
pcasarettopcasaretto

bug-reproduction-validator

Reproduce reported software issues and classify them as bugs, environmental problems, or user errors.

Community
Advanced
Vibe-Media-LabVibe-Media-Lab

fix-batch

Analyze, modify, and verify reported bugs with npm run build validation.

Official
Advanced
raydocsraydocs

memory-scout

Search .flow/memory files for relevant pitfalls, conventions, and decisions.

Community
Intermediate
alixexalixex
4

test-driven-development

Enforce Test-Driven Development by mandating failing tests before production code.

Official
Advanced