Stats
Actions
Tags
From undo
Debug programs using Undo time travel debugging. Record flaky tests, intermittent failures, race conditions, or bugs that don't reproduce reliably. Analyze recordings by traveling backwards through execution history. Use when the user mentions debugging, flaky tests, intermittent bugs, race conditions, `.undo` files (Undo recordings), or asks why something happened in an actual run. This can provide similar results as adding logging statements, but without modifying the code or needing to re-run the program multiple times.
How this skill is triggered — by the user, by Claude, or both
Slash command
/undo:debugging-with-undoThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Undo provides time travel debugging for Linux programs. This Skill guides you to:
Undo provides time travel debugging for Linux programs. This Skill guides you to:
record MCP tool)Record program execution when the user:
Undo captures the exact execution including thread interleavings, making even race conditions reproducible.
Debug a recording when the user:
.undo recording file to investigaterecord MCP tool to capture the failure.undo files directly - they are opaque binary recordingsudb, live-record, or undo via Bash - use the Undo MCP toolsnpx claudepluginhub undoio/addons --plugin undoCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.