The weekly-review skill: a Sunday reset that picks one thing
TL;DR
weekly-review is a free Claude Code skill that runs a 20-minute Sunday reset. You type /weekly-review, it pulls the real evidence of your week instead of asking you to remember it, and it writes ~/weekly-review.md with your wins, the ONE thing for next week, and three moves placed into the nights you actually have.
By Sunday it feels like you did nothing. That feeling is usually wrong, and it's what we watch people quit over in month two. Progress on a stolen-hours build is weekly, not nightly. Some nights go nowhere, and if you only ever judge yourself on a single night, you quit on a Tuesday that was always going to be a Tuesday.
weekly-review is 20 minutes on a Sunday. It goes and finds what actually happened, names why the stalled things stalled, makes you pick one thing for next week, and then makes you say out loud what you're dropping. The cut is the point. Five priorities is zero priorities.
It's one of the 55 free skills in our freeskills repo. It writes to a file that keeps every past week below the current one, so after a month you can see your own pattern instead of guessing at it.
The 20-minute Sunday reset: what shipped, the ONE thing next, three moves booked.
Install the weekly-review skill
Clone the repo once, make sure your skills folder is there, then copy this one folder into it. Three lines.
bashgit clone https://github.com/duncan-buildroom/freeskills.git
mkdir -p ~/.claude/skills
cp -r freeskills/weekly-review ~/.claude/skills/Start a new Claude Code session and it's live. That's the entire setup. Nothing to sign up for, nothing to configure.
Run it the first time
Type /weekly-review on a Sunday. It starts with evidence, not questions. It reads ~/build-log.md if you have one, checks ~/plans/ for plan files, and looks at the last seven days of a project folder if you name one. Then it reads your week back to you as a list.
After that it's a conversation. It sorts the wins, pushes for the real reason each stalled thing stalled, and asks which single result would make next week worth it. Then it asks what you're dropping, and it wants at least two things named. Everything lands in ~/weekly-review.md with three moves placed into the specific nights you told it you have.
First run with an empty log is still worth doing. It'll just ask you directly instead, and it'll tell you to start running session-wrapup at the end of each night so next Sunday has something real to read.
Run your first review with no build log yet
You don't need a month of history to start. Give it the week from memory and let it do the sorting.
/weekly-review
I don't have a build log yet. Here's my week from memory: [what you did, in any order, including the nights that went nowhere]. My project folder is [~/path/to/project]. Sort it out and tell me what actually counts as shipped.Get the ONE thing down to a real result
The most common wrong answer here is an activity, like work on the site. Push it until it's something that exists or something a person has seen.
/weekly-review
I want next week's one thing to be about [the project or outcome]. Write it as a result someone else could confirm, not as an activity, and make sure it's finishable in [the number] nights of about [90] minutes.Book the three moves into the nights you have
Three moves survive a missed night. Seven guarantee a failed week and the guilt that comes with it. Tell it your real availability before it schedules anything.
/weekly-review
The nights I actually have this week are [Tuesday and Thursday after 8pm, Saturday morning]. Place the three moves into those slots, describe each one as the outcome I'll have at the end of the sitting, and keep them all serving the one thing.The 60-second version
Here is what the Sunday reset actually does and why twenty minutes of it changes the week.
- 1Hook: there's a brand new free Claude skill that takes you from feeling like you did nothing all week to knowing exactly what you shipped and the one result you're chasing next week.
- 2Mechanism: it reads your build log and your plan files from the last seven days before it asks you anything, then reads back what you really shipped. It makes you name why each stalled thing stalled, and the answer has to be specific, not no time. Then it cuts you to one result for next week, asks what you're dropping, and puts three moves into the nights you actually have.
- 3Transformation: you stop judging a month of work by one flat Tuesday. You get a written record of what's real, and next week starts with three moves already sitting in your calendar.
- 4Close: the Sunday reset is free, and it's one of 55 free skills. If you want the weeks it's reviewing to add up to something, that's Claude Code Club at $9 a month. Link below.
Do it tonight while it's still Sunday. Run the review, then put those three moves in your calendar before you get up from the chair.
Common questions
Do I need to know how to code?
No. You answer questions about your week. The skill does the digging and writes the file.
Is it really free?
Yes. It's one of 55 free skills in the public repo. No API keys, no config, no account.
What if I don't have a build log?
It works anyway, it just asks you directly instead of reading the evidence. It will also point you at the session-wrapup skill so the log fills itself in nightly and next Sunday has more to work with.
What if I genuinely got nothing done this week?
It won't manufacture wins. It says so plainly and makes next week's one thing very small, a single visible result in one sitting, because a tiny finished thing rebuilds momentum faster than a pep talk.
Does it overwrite last week's review?
No. Each new week gets added at the top of ~/weekly-review.md and the old weeks stay below. The history is the point, and after a few weeks the honest pattern line at the bottom of each entry becomes the most useful part of the file.
Keep going
Want the whole weekly build system, not just the review?
Get 650+ plug-and-play skills, MCPs & prompts, plus 7,000+ members - $9/mo, cancel anytime.
Join the Club