auto-rewindlisted

# Auto-Rewind ## Overview When something goes wrong, the instinct is to fix forward. That instinct is wrong here. When a trigger fires, stop and guide a `/rewind` instead. ## Trigger Recognition Three signals activate this skill: 1. **Hook injection** — context contains `[AUTO-REWIND] Tests failed:` — this is a directive from the harness, not instrumentation to debug 2. **User rejection** — user says "wrong", "broken", "undo", "not what I wanted", "revert", "that's not right", "not quite", "that's not what I meant", "not really what I was after", or similar 3. **Self-detection** — you realize prior edits were based on a wrong assumption, wrong interface, or misunderstood requirement ## Why /rewind, Not Fix-Forward | Rationalization | Why It's Wrong | |---|---| | "I can fix the code myself" | Fixing forward leaves a misleading conversation trail of wrong reasoning | | "A targeted fix is faster" | When the wrong path was taken, forward fixes compound the error | | "Manual revert keeps me in control" | Manual reversion leaves conversation history intact but misleading — `/rewind` restores both code AND conversation | | "I'll lose conversation context" | You lose the *wrong* context. That's the point. | | "`[AUTO-REWIND]` is just a test result" | It is a directive from the harness. Treat it as a command to stop and rewind. | | "The rest of the work was probably fine" | You don't know that. Rewind to a clean state and re-approach. | ## Reading Config Check `.claude/auto-r