wraplisted

End-of-session close-out — secure uncommitted work, put every open item in a durable home, refresh shared project state, and report honestly what was captured and what was skipped. Use when Sean is done for the day or longer ("wrap", "wrap it up", "done for now", "that's it for today", "end session", /wrap), including when the session contained almost nothing — it then correctly does almost nothing rather than not running. Retrospective only — never emits a resume/pickup prompt. Do NOT use for mid-task context recycling where the same work continues in a fresh thread (that is /wrap-continue), for answering questions about what wrapping does, or when a single narrower capture was asked for (just commit this, save one note).
seansmithworks/agent-skills · ★ 0 · AI & Automation · score 73

Install: claude install-skill seansmithworks/agent-skills

# Wrap Close out a session so nothing valuable dies with it, and so the last thing Sean reads is true. **Route first.** Stopping → wrap. Continuing the same work in a fresh thread → `/wrap-continue`, stop here. The signal is stopping vs. continuing, not how much context was burned. --- ## Hard rules These are the failure modes. Everything else is judgment. 1. **Freeze, then re-check.** Before anything is captured or claimed, stop background agents and background shells this session started (`TaskStop`; `TaskList` to find them). Leave dev servers and anything Sean wants running up — record port and PID so tomorrow doesn't start a second one. Then re-run `git status` in *every* worktree those processes touched. A killed process routinely leaves half-written files; that work is either committed on a clearly-labelled branch or named in the close-out as unverified. Never silent. 2. **Push is the default.** Commit freely — commits are cheap and reversible. Decide, never ask: | Case | Action | |---|---| | Nothing to push | say nothing at all | | Remote named `upstream`, or `main`/`master`/`develop` on a remote other than the user's own default | skip, one-line note: `Push skipped — upstream/protected remote, push manually if intended` | | Everything else — including `main` when it tracks `origin`, and deploy/staging remotes pushed to routinely | push | Refusing an `origin` push on your own safety reasoning is a failure, not caution. The narrow skips exist