🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
πŸ¦€ ClawHub

Fix

by @drumrobot

User behavior correction skill. Triggered by "fix:" prefix feedback (e.g., "fix: why didn't you commit?"). Analyzes the mistake, improves the relevant prompt...

Versionv0.3.0
Downloads1,125
TERMINAL
clawhub install fix

πŸ“– About This Skill


metadata: author: es6kr version: "0.1.4" name: fix description: >- User behavior correction skill. Triggered by "fix:" prefix feedback (e.g., "fix: why didn't you commit?"). Analyzes the mistake, improves the relevant rule/skill/hook to prevent recurrence, then fixes the current issue. TodoWrite required for all steps. Use when "fix:", "fix this", "correct", "why not", "why missing", "behavior fix" is mentioned.

Fix: Behavior Correction Skill

Activated when user gives feedback with "fix:" prefix. Finds the root cause of the mistake, improves rules/skills/hooks, and fixes the current issue.

Trigger

  • Messages with fix: prefix
  • Behavior correction feedback: "fix this", "correct", "why not", "why missing"
  • Procedure

    Step 0. TodoWrite (MANDATORY β€” first action, no exceptions)

    Before any analysis or text output, register TODO items:

    TodoWrite([
      { id: "fix-0", content: "fix: {user feedback summary} β€” root cause analysis", status: "in_progress" },
      { id: "fix-1", content: "Root cause fix", status: "pending" },
      { id: "fix-2", content: "Fix current issue", status: "pending" },
      { id: "fix-3", content: "Completion report + cleanup", status: "pending" },
    ])
    

    Step 0 is the first tool call after /fix activation. Text output before TodoWrite = violation.

    1. Root Cause Analysis (5-Why depth)

    Don't stop at the direct cause. Dig at least 3 levels deep:

    Why 1: What went wrong? (symptom β€” the immediate mistake)
    Why 2: Why did I make that decision? (judgment β€” missing knowledge/rule)
    Why 3: Why was that knowledge/rule missing? (structural β€” skill/rule gap)
    

  • Fixing only Why 1 = patching a symptom. It recurs in a different form.
  • Why 2-3 reveal structural causes (platform ignorance, DRY violation, etc.) β€” these go into rules/skills.
  • Search for the responsible skill/rule/hook files (Grep/Glob)
  • 2. Root Cause Fix (Prevent Recurrence)

    Priority (check in order β€” stop at the first match):

    | Priority | Target | Condition | Example | |----------|--------|-----------|---------| | 1st | Skill (~/.claude/skills/, .claude/skills/) | Skill is incomplete or has wrong procedure | Fix procedure step missing | | 2nd | Rule (~/.agent/rules/, .claude/rules/) | Behavior rule is missing or insufficient | Add to failed-attempts.md | | 3rd | Hook (settings.json hooks) | Automation needed for repeated mistakes | Add PostToolUse hook | | 4th | SKILL.md docs | Documentation doesn't match actual behavior | Update section |

    When fixing:

  • Skill is 1st priority β€” if the problem is a skill's incomplete procedure, fix the skill. Don't skip to failed-attempts.md
  • Skill improvements must follow skill-kit upgrade procedure (direct script/topic file edits allowed)
  • Rule location must be confirmed via AskUserQuestion
  • failed-attempts.md recording is only for cases not covered by skill/rule/hook β€” no duplicate recording if root cause is already reflected in a skill or rule
  • 3. Fix Current Issue + Resume Original Work

  • After root cause fix, immediately resolve the current problem
  • If unsure what to execute, AskUserQuestion β€” don't skip execution because you don't know the command
  • Verify fix results (build/test/run)
  • Continue the originally intended work with the corrected approach β€” don't just clean up wrong artifacts, complete the original task
  • Resume the originally intended work with the corrected approach
  • 4. Completion Report + Cleanup

    Fix complete:
    
  • Root cause: {what was missing}
  • Improvement: {which file was modified and how}
  • Current fix: {result of fixing the current issue}
  • After reporting, delete all TODO items created in Step 0 β€” fix TODOs are temporary session-level tracking only; must not persist after completion.

    Anti-patterns

  • Repeating "already fixed" without actually fixing the root cause
  • Patching only the current issue without improving skills/rules/hooks
  • Text response without TodoWrite after /fix activation
  • Recording in failed-attempts.md when the root cause is a skill defect (skill fix is 1st priority)
  • Stopping at Why 1 β€” fixing the symptom without asking Why 2-3 (structural cause)
  • Not cleaning up TODO/Task after completion β€” must delete all fix TODOs when done