hatch3r-bug-fix

Diagnose software bugs and implement minimal fixes with regression tests.

26|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-bug-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hatch3r-bug-fix
Source: https://github.com/hatch3r/hatch3r/tree/main/skills/hatch3r-bug-fix
Command: npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-bug-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn an unclear bug report into a verified fix by diagnosing the root cause, implementing the smallest safe change, and proving the outcome with a regression test.

Core Features & Use Cases

  • Root-cause guided diagnosis: Produce a diagnosis plan including hypotheses, files to investigate, reproduction strategy, risks, and confidence before making changes.
  • Minimal, test-backed implementation: Prefer writing a failing regression test before the fix when the root cause is clear, then implement the minimal change to make the test pass.
  • Verification for both code and UI: Run the standard lint/typecheck/test workflow and optionally perform browser reproduction and screenshot-based confirmation for UI bugs.
  • Safe delegation and review readiness: Ensures required sub-agents are spawned at the right phases (researcher before implementation, test-writer after, reviewer after implementation) when invoked through this workflow.

Quick Start

Ask hatch3r-bug-fix to fix the reported bug using the provided issue details, then verify the fix by running tests and opening a PR with a rollback plan if needed.

Frequently Asked Questions about hatch3r-bug-fix

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

FAQPage Schema
How do I fix a bug when the reproduction steps are incomplete or unclear?

To fix a bug with incomplete reproduction steps, start by generating a structured diagnosis plan that maps out hypotheses, files to investigate, and reproduction risks before writing any code changes.

What is the best way to ensure a bug fix does not introduce regressions?

The best way to prevent regressions is to write a failing regression test before applying the fix, then implement a minimal diff change to make the test pass, followed by running lint, typecheck, and full test execution.

How do I diagnose the root cause of a software issue before making code changes?

Diagnose the root cause of a software issue by creating a structured diagnosis plan that includes potential hypotheses, files to investigate, a reproduction strategy, and a confidence assessment before modifying the codebase.

Can I use a test-first approach for both backend code and UI bug fixes?

Yes, a test-first approach works for both backend and UI bug fixes, where UI issues additionally benefit from optional browser reproduction and screenshot-based confirmation to verify visual behavior alongside standard test execution.

Does structured bug fixing require spawning sub-agents at specific phases?

Structured bug fixing requires spawning sub-agents at specific phases, including a researcher before implementation, a test-writer after the diagnosis, and a reviewer after implementation, to ensure safe delegation and review readiness.