The safety-net skill: two undos, so you can experiment
TL;DR
The safety-net skill sets up both of your undos and makes you use them once: /rewind for instant undo, and Git checkpoints for permanent saves you can name. It makes your first checkpoint on the project you have open right now and leaves a one-page cheat sheet at ~/claude-safety-net.md with the exact recovery moves.
Most beginners build timidly, because they think one bad prompt can wreck the whole thing. So they never try the interesting version. They keep the layout that works and quietly avoid the one they actually want.
You've got two separate undo systems and they do different jobs. /rewind is instant and automatic, and it's for when the last thing you did made things worse. Git checkpoints are permanent and you ask for them by name, and they're for getting back to how it was on Tuesday. The safety-net skill explains both, makes your first real checkpoint on the project you have open, and leaves you a cheat sheet.
One line holds the difference: rewind undoes moves, checkpoints save days. It's free, it's in our public freeskills repo, and the README puts it in week one on purpose.
Sets up both undos so you can experiment without guarding the working version.
Install the safety-net skill
It's the same three lines as every skill in this repo. Clone, make the folder, copy.
bashgit clone https://github.com/duncan-buildroom/freeskills.git
mkdir -p ~/.claude/skills
cp -r freeskills/safety-net ~/.claude/skills/Open a new session and it works. No configuration, no API keys, nothing else to set up.
Run it the first time
Type /safety-net with a real project open, because this one does things rather than describing them. It tells you the difference between the two undos, then has you actually test /rewind: ask Claude for one pointless change, like turning a heading into the word BANANA, look at it, then put it back. Doing that once removes the fear in a way that reading about it never does.
Then it checks whether your project is set up for checkpoints, sets it up for you if it isn't, and gets you to make your first one by saying a single sentence to Claude. You never type a Git command. It finishes by writing a one-page cheat sheet to ~/claude-safety-net.md with the recovery moves word for word, plus the name and date of the checkpoint you just made. It takes about ten minutes, and one of those is the BANANA test.
Make your first checkpoint tonight
The checkpoint is the part that has to actually happen. Run this on the project you care about most, not a test folder.
/safety-net
I'm working on [project name] at [folder path]. It works right now and I don't want to lose this version. Set up whatever's needed, then walk me through making my first checkpoint on it. I've never used Git and I don't want to type commands.Do the test that kills the fear
Reading about an undo button doesn't make you brave. Pressing it does. Break something on purpose, put it back, and then go build like someone who isn't worried.
/safety-net
I want to test rewind before I trust it. Make one small pointless change to [the file or page], something obvious I'll see straight away. Tell me exactly what to look for. Then tell me the keys to press to put it back, and confirm with me that it's back.Get back to when it worked without losing today
This is the situation people panic in: the old version was better, but you don't want to throw away the last three hours either. You don't have to pick.
/safety-net
My project was working [when, e.g. this morning] and now it isn't. I want the working version back, but I also want to keep what I've made since then so I can look at it. Save what I have now as a checkpoint first, then take me back to the good one, and tell me how to find today's work again afterwards.The 60-second version
Here is what this skill does and why it is the one to do before anything risky.
- 1Hook: there's a brand new free Claude skill that takes you from building scared to two undo buttons you've actually tested.
- 2Mechanism: you tell it which project you're working on and it sets up both undo systems on that real project, not on an example. It walks you through breaking something on purpose and putting it back, then saves a permanent checkpoint with a name while you watch. What lands is a one-page cheat sheet with the exact words to say for I broke it, go back one step, and go back to when it worked.
- 3Transformation: you stop protecting the version that works and start trying the version you actually want. Nothing you do after tonight can cost you more than a few minutes.
- 4Close: both undos cost you nothing, and this is one of 55 free skills. If you want the whole path you're now safe to build on, Claude Code Club is $9 a month. Link below.
Run it tonight on your real project and make the checkpoint. Then go try the redesign you've been avoiding, because now the good version is saved.
Common questions
Do I need to know Git?
No, and the skill won't hand you commands. You say one sentence to Claude and Claude does it. If your project isn't set up for checkpoints yet, the skill sets it up for you.
What's the difference between rewind and a checkpoint?
Rewind is automatic and instant, for the last thing you did in this session. A checkpoint is one you ask for by name and it's saved permanently, for getting back to a state from days ago. Rewind undoes moves, checkpoints save days.
Do I have to set rewind up?
No. Claude Code takes a snapshot before every change it makes, whether you ask or not. Type /rewind, or press Esc twice with an empty input box.
I've already broken something. Can I still use this?
Yes. Tell it that up front and it handles the recovery first, then sets the rest up afterwards.
Is it really free?
Yes. The repo is public and you can copy or edit any of it. Nothing here bills you and nothing asks for a key.
Keep going
Want to build without guarding every working version?
Get 650+ plug-and-play skills, MCPs & prompts, plus 7,000+ members - $9/mo, cancel anytime.
Join the Club