fix-bug

Diagnose and fix software bugs using hypothesis-driven analysis and minimal fixes.

30|2|Updated Apr 28, 2026

Search Tags:#debugging #codebase #diagnose #triage #hypothesis #root-cause #bug

Ready to run

npx skills add https://github.com/hawkyre/hawk-skills --skill fix-bug-hawkyre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-bug
Source: https://github.com/hawkyre/hawk-skills/tree/main/skills/fix-bug
Command: npx skills add https://github.com/hawkyre/hawk-skills --skill fix-bug-hawkyre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, hypothesis-driven approach to diagnosing and fixing bugs in software systems, combining symptom collection, multiple root-cause hypotheses, and a minimal, verifiable fix.

Core Features & Use Cases

Structured triage: collects symptoms, environment details, and reproduction steps to inform hypotheses.
Hypothesis-driven debugging: generates and tests root-cause hypotheses before making changes.
Minimal-fix discipline: implements the smallest change that resolves the issue and validates it with tests.

Quick Start

Describe the bug symptoms, environment, and reproduction steps, then generate hypotheses, investigate top candidates, and implement the minimal fix.

Frequently Asked Questions about fix-bug

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

FAQPage Schema

What is hypothesis-driven debugging and how does it help fix bugs faster?▼

Hypothesis-driven debugging generates and tests multiple root-cause hypotheses before making changes, ensuring you fix the actual bug rather than symptoms. It provides a structured triage process to collect environment details and reproduction steps for accurate diagnosis.

How do I diagnose a bug from user-reported symptoms and error logs?▼

Diagnose a bug by collecting reported symptoms, environment details, and reproduction steps into a structured triage. Generate root-cause hypotheses, investigate top candidates in the codebase, and implement the minimal verifiable fix to resolve the issue.

Does this debugging approach work across different programming languages and dependencies?▼

Yes, this debugging approach applies to codebases across languages and dependencies. It guides the workflow from triage to minimal fix using symptom collection and hypothesis generation, accommodating diverse software systems without language-specific constraints.

What is the best way to fix a bug without introducing regressions?▼

The best way to fix a bug without regressions is applying minimal-fix discipline: implement the smallest change that resolves the issue, then validate with tests. Post-fix verification and logging guardrails ensure the fix prevents future regressions.

Can I use online research during the codebase debugging workflow?▼

Yes, online research is triggered during the debugging workflow when needed. After symptom collection and hypothesis generation, the process incorporates online research before focused code investigation to help identify root causes in unfamiliar dependencies.

When should I not use a structured debugging process for my codebase?▼

You should avoid a structured debugging process for trivial syntax errors requiring immediate fixes. The hypothesis-driven approach adds overhead through triage, hypothesis generation, and post-fix verification, making it best suited for complex bugs with unclear root causes.