fix

Diagnose software defects and implement validated incremental fixes.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/donygeorge/claude-toolkit --skill fix-donygeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/donygeorge/claude-toolkit/tree/main/skills/fix
Command: npx skills add https://github.com/donygeorge/claude-toolkit --skill fix-donygeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically addresses the common pain point of debugging and bug management by providing a repeatable, safe workflow from root-cause analysis to validated fixes, reducing time to resolution and regression risk.

Core Features & Use Cases

  • Root-cause investigation: Identify the underlying cause before proposing changes.
  • Reproduction & validation: Reproduce defects to verify symptoms and confirm fixes.
  • Safe, incremental fixes: Apply minimal changes with testing and clear rollback guidance.
  • Use case: A team uses this workflow to resolve intermittent bugs without GitHub issues blocking triage.

Quick Start

Describe the bug, reproduce it locally, implement a minimal fix, run tests, and commit.

Frequently Asked Questions about fix

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

FAQPage Schema
What is a structured bug-fix workflow for diagnosing software defects?

A structured bug-fix workflow systematically guides root-cause analysis, reproduction, pattern scanning, and safe incremental fixes across codebases to reduce resolution time and regression risk.

How do I reproduce a bug and find the root cause before applying a fix?

You reproduce a bug and find the root cause by locally validating symptoms, scanning for error patterns, and testing hypotheses before implementing minimal code changes.

Can I use a systematic debugging workflow for bugs without GitHub issues?

Yes, you can apply a systematic debugging workflow to diagnose defects without GitHub issues by following enforced phases for root cause identification, hypothesis testing, and implementation.

What is the best way to apply safe incremental fixes during debugging?

The best way to apply safe incremental fixes is to enforce test-first guidance, validate changes, and follow strict escalation rules with clear rollback guidance to minimize regression risk.

When should I not use a full 4-phase debugging workflow?

You should not use a full 4-phase debugging workflow for trivial cosmetic changes or typo corrections where root-cause analysis and pattern scanning provide no meaningful validation value.