The session-wrapup skill: end tonight so tomorrow starts fast
TL;DR
session-wrapup is the free skill you run in the last ten minutes of a build night. You type /session-wrapup, it goes and checks the project itself rather than asking you what you did, and it appends a dated entry to ~/build-log.md ending in one specific first move for tomorrow. It's the reason a build survives a two-day gap.
Most builds don't die from a hard bug. They die from a cold reopen. You build for 90 minutes on Tuesday, close the laptop, come back Thursday, and spend the first half hour re-reading files and re-explaining the project before you touch anything. Do that four times and the build is over.
session-wrapup is the last ten minutes of the night. It looks at what actually changed, sorts it into what's working and what's half-done, and writes one line telling tomorrow-you where to pick up. It writes one line, not a to-do list. Three things at the bottom of a log get read and none of them get started.
It's one of the 55 free skills in our freeskills repo, and it writes to a real file on your machine, so the record builds up night after night instead of vanishing with the chat.
Ends the build night with a dated log entry and one first move for tomorrow.
Install the session-wrapup skill
Three lines. Clone the repo, make sure your skills folder exists, then copy the one folder you want into it.
bashgit clone https://github.com/duncan-buildroom/freeskills.git
mkdir -p ~/.claude/skills
cp -r freeskills/session-wrapup ~/.claude/skills/Restart Claude Code, or just open a new session. That's the whole install. No API keys, no config.
Run it the first time
Type /session-wrapup at the end of a build night. It won't start by asking what you did, because you were watching loosely and you'd under-report. It confirms the folder, goes and looks at which files changed if the project is set up for checkpoints, reads back over the session, and states what changed in three to six plain lines.
Then it splits the work into two piles. Working means you or it actually looked at the thing and saw it behave. Half-done means started and not finished, or finished and not checked, with one clause on what's missing. It prompts you to save a checkpoint, appends a dated entry to ~/build-log.md, and ends by saying tomorrow's first move out loud.
A good first run feels a bit strict. If you never opened the page on your phone, the phone layout goes in half-done. That honesty is the whole value, so don't argue it up into the working pile.
Wrap up a night that went badly
Messy sessions are the ones most worth logging, and the ones people skip. Tell it the truth about the state you're in.
/session-wrapup
I worked on [project name] for about [90] minutes tonight and it's a mess: [what's broken or confusing right now]. Log it honestly, don't dress it up, and give me one small first move for tomorrow.Wrap up a project that isn't a git repo
Plenty of first builds are just a folder with one HTML file in it. Point the skill at it and it works the same way.
/session-wrapup
The project lives at [~/path/to/your/project] and it isn't a git repo. Here's what I changed tonight: [two or three lines]. Check which files were modified today, then write the entry.Get a first move you can start cold
The line at the bottom of the entry is the most valuable thing the skill produces. Size it to the time you'll actually have.
/session-wrapup
I've got about [75] minutes tomorrow and I'll have forgotten everything by then. Make the first move small enough to fit that, and write it so I could start it without reading anything else first.The 60-second version
Here is what this skill does at the end of a night, and why that ten minutes pays for itself.
- 1Hook: there's a brand new free Claude skill that takes you from opening a project two days later with no idea where you left off, to being back in the build in five minutes.
- 2Mechanism: you hand it the night you just had, and it goes and checks the project itself rather than taking your word for what changed. It sorts everything into what's working and what's half-done, and it's strict about the difference. Then it writes a dated entry to your build log with one specific sentence for tomorrow's first move, and asks you to save a checkpoint before you close the laptop.
- 3Transformation: your build stops resetting every time life gets in the way. You sit down, read one line, and start. The 90 minutes you have go into building instead of remembering.
- 4Close: it's free and it's one of 55 in the repo. This one keeps one night from getting lost. If you want the path that all those nights are supposed to add up to, Claude Code Club is $9 a month. Link below.
Do this tonight, even if the session went nowhere. Then tomorrow, open ~/build-log.md first, do the one move at the bottom, and nothing else.
Common questions
Do I need to know how to code?
No. The skill goes and looks at the project itself, writes the entry, and tells you the file path. You answer a question or two and read the line for tomorrow.
Is it really free?
Yes. It's one of 55 free skills in the public repo. No API keys, no config, no account to make.
What if my project isn't a git repo?
It still works. Without git it lists the files and checks what was modified today. You can also just tell it in a couple of lines what you changed.
What is the checkpoint it asks for?
A permanent snapshot of tonight's work, so any future mistake can be undone back to this exact state. You say the word and Claude saves it. If you'd rather not, the skill notes in the log that there wasn't one and moves on.
What if nothing worked tonight?
Log it anyway. The skill records a bad night honestly, and tomorrow's first move becomes something tiny, like describing what you see on the screen. That's a perfectly good starting point.
Keep going
Want the whole build habit, not just the wrap-up?
Get 650+ plug-and-play skills, MCPs & prompts, plus 7,000+ members - $9/mo, cancel anytime.
Join the Club