Close out a session without leaving it half-shipped.

“Is this work actually shipped, live, and safe to walk away from, or just done on my machine?”

Verifies every change is committed, pushed, and green, confirms it is live, updates the notes, and hands back a summary with a rollback path.

RUN THE OPERATOR SYSTEMADVANCED✓ APPROVED 4/4
EXAMPLE PROMPTS
>Close out this session. Check everything is committed, pushed, and live
>Are we good to close? Verify the deploy is green and tell me the rollback path
>Run session QA and update the notes so the next session starts warm
ABOUT THIS SKILL

What this skill does

Runs the safety pass at the end of a work session so you never leave the work half-shipped. It checks that everything is committed and pushed, the build or deploy is green, the change is actually live and verified, and the notes are updated so the next session starts warm. Then it hands you a short summary with live links, open items, and how to roll back. It is the lock-up, not the learning pass. Pair it with a handoff note and a reflect pass.

Inputs

  • Works today with: a plain list of what you changed and where it should be live. Paste it.
  • More powerful with a git repo: it reads status, the branch, and whether local matches the remote.
  • Sharper with CI or a deploy target: it confirms the build is green on the right commit before it calls it done.

How it works

  1. 1
    1. Inventory what changed

    List every change this session and where each is supposed to show up. Anything not on the list does not get verified, so the list has to be honest.

  2. 2
    2. Commit and push

    Confirm the working tree is clean, everything is committed with a real message, and local matches the remote. Uncommitted work is the most common way a session is lost.

  3. 3
    3. Confirm green

    If there is a build, CI, or deploy, confirm it is passing on the exact commit you pushed. Not a previous one.

  4. 4
    4. Verify live

    Actually load the thing. Check the change is present in production, not just in the diff. For anything visual, look at it.

  5. 5
    5. Update the notes

    Write the next-session brief: current state, open items, where things live. Convert any "today" to a real date.

  6. 6
    6. Hand back the summary

    Report what shipped with live links, what is still open, and the one command or commit to roll back if needed.

Output format

CLOSEOUT: green
Shipped:
- New pricing page, live at /pricing (verified)
- Fixed the signup redirect (verified, tested)
Committed + pushed: main @ a1b2c3d, matches origin
Deploy: READY on a1b2c3d
Open items: mobile spacing on the hero (not blocking)
Rollback: revert to 9f8e7d6

Tips

  • Nothing is reported as done unless it was confirmed live. Unverifiable items are flagged.
  • Local must match the remote before closeout passes.
  • The summary always includes a rollback path.
  • Closeout is the safety pass only. It does not rewrite the work or the skills; that is the reflect pass.
RELATED SKILLS
NO SETUPEASY · Operator System & Context

Turn a cold start into a warm one with one doc.

A single pack that tells a new session or teammate what the project is, where things live, what's decided, and the next move.

RUNS ON WHAT YOU PASTEAPPROVED · INSTALL →
NO SETUPEASY · Operator System & Context

Capture the session context so you can resume it cold.

An end-of-session brief: progress, decisions, unfinished items with next steps, and the fragile details, then it asks whether to save.

RUNS ON WHAT YOU PASTEAPPROVED · INSTALL →
ALL RUN THE OPERATOR SYSTEM SKILLS →