Stats
Actions
Tags
From havn
Use when fixing a bug, resolving an error, or addressing unexpected behavior. Triggers on "fix", "debug", "broken", "regression", "not working".
How this skill is triggered — by the user, by Claude, or both
Slash command
/havn:fix-bugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reproduce, test, fix, verify. The regression test is the deliverable — the fix is secondary.
Reproduce, test, fix, verify. The regression test is the deliverable — the fix is secondary.
Confirm the bug exists. Find or create a minimal reproduction. If it cannot be reproduced, gather more information before proceeding.
Read the code path. Form a hypothesis. Verify with targeted code reading, test instrumentation, or print debugging — do not guess. The fix should target the cause, not the symptom.
Write a test that fails with the current buggy code. This test proves the bug exists and prevents reintroduction. Run it — confirm it fails for the right reason.
Change the minimum code to make the regression test pass. Do not refactor surrounding code or fix unrelated issues in the same change — scope creep masks regressions.
Run the full test suite. Compare to baseline in project memory. The fix must not break existing behavior.
npx claudepluginhub phibkro/vevx --plugin havnWrites a failing automated test that reproduces a bug before fixing it, then verifies the fix passes. Use when fixing any bug to prevent silent recurrence.
Diagnoses and fixes bugs using a test-first workflow: reproduce with a failing test, diagnose root cause, then fix. Activates on bug reports, unexpected behavior, or defect investigations.
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.