The /wrapup discipline
Full Lesson Reference
/wrapup is 30 seconds that saves 15 minutes on your next session. The single highest-impact habit you build in Claude Code. This lesson is about making it automatic.
What /wrapup actually does
When you run /wrapup, it
- Summarises the session - what you worked on, key moves, outcomes
- Captures decisions - what you chose and why
- Logs rules learned - preferences or patterns that emerged
- Lists pending items - what's left for next time
- Saves to Supabase - all of the above becomes a session_memories row
- Updates project record - if you're in a project, the projects table gets the latest context
- Commits + pushes - your code/file changes go to GitHub so nothing's lost
All automatic. You run one command. Claude does the rest.
What happens without it
Skip /wrapup and
- Next session has zero memory of what you did
- Your Supabase memory stays empty - nothing to search, nothing to load
- File changes might not be committed (they're still on your machine, but nothing's in GitHub)
- You spend the first 10-15 minutes of the next session re-explaining context
For every 10 sessions where you skip /wrapup, you've lost ~2 hours to ramp-up. For every 100 sessions skipped, 20 hours.
When to run it
Every session end
Non-negotiable. Before you close the terminal, /wrapup runs.
Mid-session, before a big task
If you've been in a session for hours and context is approaching 50%, wrap up and start fresh before the next big task. The fresh session starts lean.
When switching projects
Going from Client A to Client B? /wrapup on A first, close, open B's folder, /startup on B.
When you're about to close your laptop
If you're done for the day and haven't wrapped up yet - do it now. Laptop crashes, power outages, accidental closes all happen. Unsaved sessions lose everything.
What a good /wrapup looks like
Good /wrapup summaries are specific and decision-oriented. Bad ones are vague and list-y.
Bad
Summary: Worked on the client report. Actions: Built the report. Pending: Continue next time.
Tells future-you nothing useful.
Good
Summary: Built the Q2 weekly report for client X. Focused on the shift from Meta to Google Ads efficiency. Report uses the standard performance-reporting template.
Decisions
- Included the ROAS trend chart (client requested in last call)
- Excluded Meta breakdown below $50 spend (noise)
- Used last 13 months for comparison, not 12 (matches YoY period)
Rules learned
- Client X prefers ROAS over CPA as primary metric
- No bullet points in report intros - they want prose
Pending
- Send report Friday morning AEST
- Next week, pull Shopify revenue attribution
- Open question: whether to include branded search conversions
Future-you picks up in 30 seconds instead of 15 minutes.
How to prompt a good /wrapup
Before running /wrapup, prime it with
Before you wrap up - summarise the key decisions we made and the reasoning behind each. List anything I should remember for next session even if it feels obvious. Then run /wrapup with that context.
Gives Claude a clearer snapshot to save.
Power-user tips
- Don't run /wrapup if the session was unproductive - if you tried something and it didn't work, that's worth saving. But if you didn't actually do anything, just close the session. Saves the memory layer from noise.
- Add "don't forget" items as you go - mid-session, tell Claude "add to pending items: check the analytics conversion tag on the new page". /wrapup picks these up at the end.
- Review the summary before confirming - /wrapup shows you what it's about to save. Read it. If it's wrong, tell Claude to rewrite before saving.
- Wrap up is commit discipline too - treat /wrapup as your end-of-session commit. Never leave changes uncommitted on your machine.
Action items
☐ Commit to /wrapup on every session end. Zero exceptions.
☐ Prime /wrapup with a decision summary before running it
☐ Review the summary before confirming the save
☐ Add pending items to the session as you go - /wrapup captures them Next lesson: Multi-session workflows.
Exercises
- Review the concepts covered in this lesson: The /wrapup discipline.
- Write down your key takeaway from this lesson.
- Practice running any commands or prompts mentioned above inside your terminal.