Busy is not the same as done
Long sessions drift. You asked for one thing, twenty tool calls later a lot happened, and nobody checked whether the thing you asked for actually landed. This skill checks.
How it works
01 Finds your original ask The first thing you asked for, not the last.
02 Checks the evidence Git, files on disk, test runs. Not memory.
03 Gives a straight verdict Yes, partial or no. No hedging.
04 Lists what's still open As decisions you need to make, not questions.
What you get back
- Original intentAdd Stripe webhooks to the booking flow.
- Accomplished: PartialThe webhook handler is written and deployed. It was never tested with a real event.
- Also happenedFixed the email template. Cleaned up two old branches.
- Open loopsNeeds your go to send one live test payment.
Sample report, for illustration.
Copy. Paste. Done.
Paste this into Claude Code. It installs the skill and checks it worked.
Install the session-close skill from https://github.com/ezjonline/ezj-automations/tree/main/skills/session-close into my Claude Code skills directory. Clone https://github.com/ezjonline/ezj-automations, copy the skills/session-close folder to ~/.claude/skills/session-close, then confirm the skill is available.- 3 verdicts: yes, partial, no
- 60 sec to read
- 0 files written
Use it
At the end of any session, type /session-close. If the answer is partial, you know exactly what to finish before you move on.
Free AI Audit
Want the whole system, not just the skill?
This is one piece of how I run my business. Book a free AI Audit and I'll map out what the full setup looks like for yours.
Get my free AI Audit