Wrap Up (finalize the work product)

This skill finalizes the deliverable at the end of a work session: makes the changes durable and shippable (build green, versions/changelog, docs, gated commit) and leaves things in a known-good state.

It is NOT /handoff. /handoff preserves the conversation (a throwaway doc so you can /clear) and never changes code. /wrapup touches real shipped state. They compose: run /wrapup first to finalize, then /handoff if you're about to /clear.

How to run it: a reporting checklist, not a blind auto-runner

Walk the steps in order. For each, report status — ✅ done / ⏭️ skipped (why) / ⚠️ needs the user. Never silently auto-do the gated item (commit). End with a one-screen summary table.

Steps

1. Build / lint / test green

• Run the project's checks before declaring done — detect from the repo: npm test / pnpm test, cargo test, go test ./..., pytest, make, ./gradlew build, etc. If you can't tell, ask which to run rather than skipping silently.
• If something fails, say so with the output — don't call it done.

2. Version / changelog (only if the project uses one)

• If the repo versions releases (a version in package.json/Cargo.toml/pyproject.toml, a CHANGELOG.md, tags), bump/append per its convention. If it doesn't, ⏭️ skip and say so.

3. Docs

• If behavior changed, update the affected README / docs — usage, flags, examples. Keep it to what actually changed.

4. Notes / lessons (if the repo keeps them)

• If the session produced a reusable gotcha or fix pattern and the repo has a NOTES.md / LESSONS.md / decision log, add a short entry with the evidence that proved it. Otherwise skip.

5. Commit — GATED

• Do NOT git commit or git push unless the user explicitly asks. If they didn't, report "uncommitted — say the word to commit" and stop here. (Use /commitpush when they do.)
• When you do commit: stage only the relevant files/hunks — never sweep in unrelated dirty changes. Fold the docs/notes from steps 3–4 into the same commit.

6. Worktree cleanup (if you use worktrees) — GATED

• If this topic had its own git worktree + branch and it's now fully merged, it's dead weight. Verify before pruning — never on a hunch:

  git log --oneline <integration-branch>..<branch>   # EMPTY = fully merged, nothing unshipped

  Only when empty, and only on the user's okay:

  git worktree remove <path>
  git branch -d <branch>        # -d refuses if unmerged; never -D unless the user confirms

• Never remove a worktree with uncommitted changes (another chat may be mid-edit there).

7. Close out

• Print the summary table (item → ✅/⏭️/⚠️ + one line).
• If the session is heading toward a /clear, offer /handoff — don't write the handoff yourself.

Don'ts

• Don't write a handoff doc — that's /handoff. This skill finalizes shipped state, not context.
• Don't commit or push unless explicitly asked. Report the uncommitted state instead.
• Don't stage unrelated dirty files — focused commits only.
• Don't claim "done & tested" when checks didn't run or didn't pass — say which it is.