Guides
Practical pages for working with Claude Code: seeing what a turn changed, taking it back, and keeping destructive commands in check. Each one says where its facts come from, and what turnslip does not do.
- Claude Code deleted my files: what can still come back git, /rewind, editor history, backups and recovery tools, in the order to try them.
- Stop Claude Code from running rm -rf and git reset --hard Ask rules, a PreToolUse hook, what they miss, and a backstop.
- Review what Claude Code changed before you commit /diff, the files a shell command changed, git status and diff, and staging only what you read.
- Claude Code wrote an API key into my code: find it, rotate it Rotate first, find every copy, take it out of the code and history, and keep Claude away from .env.
- What /rewind misses: a measured test rm, mv, sed -i, npm install and a Write edit, each followed by /rewind and by /turnslip:undo.
- What did Claude Code just change? Tool calls, git, and a per-turn record that includes shell commands.
- How to undo Claude Code changes What /rewind restores and misses, when git helps, and an undo that covers shell commands.
Related: Install turnslip, free