From hatch3r
Executes step-by-step bug fix workflow: read issue, diagnose root cause, reproduce (browser for UI bugs), minimal fix, regression test, verify, open PR.
npx claudepluginhub hatch3r/hatch3rThis skill uses the workspace's default tool permissions.
> **Note:** Commands below use `npm` as an example. Substitute with your project's package manager (`yarn`, `pnpm`, `bun`) or build tool when your project uses a different package manager.
Fixes bugs via root cause diagnosis with debugger/gap-analyzer, requirements.md generation, /execute delegation, 3-retry circuit breaker, and QA.
Fixes bugs using test-first loop: add minimal failing reproduction test, apply smallest fix to affected module, verify full test suite and linters. Use for reported bugs needing verified low-impact fixes.
Fixes bugs and regressions: investigates root cause with GitHub issues/grep/git, applies minimal changes, adds type-appropriate regression tests, verifies tests, reviews code and tests via gates.
Share bugs, ideas, or general feedback.
Note: Commands below use
npmas an example. Substitute with your project's package manager (yarn,pnpm,bun) or build tool when your project uses a different package manager.
Task Progress:
- [ ] Step 1: Read the issue and relevant specs
- [ ] Step 2: Produce a diagnosis plan
- [ ] Step 2b: Browser reproduction (if UI bug)
- [ ] Step 2c: Test-first approach (TDD alternative — optional)
- [ ] Step 3: Implement minimal fix
- [ ] Step 4: Write regression test
- [ ] Step 5: Verify all tests pass
- [ ] Step 5b: Browser verification (if UI bug)
- [ ] Step 6: Open PR
Before fixing, output:
Skip this step if the bug has no visual or interactive symptoms.
When the root cause is clear from diagnosis, write the regression test BEFORE implementing the fix:
This approach guarantees the fix addresses the actual bug and prevents regression. Prefer TDD when:
Skip TDD and use the standard flow (Steps 3→4) when:
npm run lint && npm run typecheck && npm run test
Skip this step if the bug had no visual or interactive symptoms.
Use the project's PR template. Include:
Note: When this skill is invoked via the orchestration pipeline (board-pickup or workflow commands), skip this section — the orchestrator handles agent delegation in Phases 3 and 4.
You MUST spawn these agents via the Task tool (subagent_type: "generalPurpose") at the appropriate points:
hatch3r-researcher — MUST spawn before implementation with modes symptom-trace, root-cause, codebase-impact. For Tier 2+ tasks (per hatch3r-deep-context), also include requirements-elicitation (bugs often have underspecified reproduction steps and ambiguous expected behavior). Skip only for trivially simple bugs (risk:low AND priority:p3).hatch3r-test-writer — MUST spawn after fix implementation to write regression tests covering the fixed behavior and related edge cases.hatch3r-reviewer — MUST spawn after implementation for code review before PR creation.hatch3r-qa-validation — use this skill for end-to-end verification of the bug fix