wrapup

name	wrapup
description	End-of-session ritual — summarize work, update docs, draft commit message
allowed-tools	Bash, Read, Write, Edit, Glob

End-of-Session Wrap-Up

You are running the end-of-session ritual for this project. Work through each step in order. Do not skip steps. After each file update, show the proposed changes and wait for confirmation before writing.

---

Step 1 — Read project context

Read the following files if they exist in the current directory:

• CLAUDE.md
• DECISIONS.md

Note their current content — you will propose updates to them below.

---

Step 2 — Summarize today's work from git

Run:

git diff HEAD

If the diff is empty, run:

git diff --staged

If both are empty, run:

git log --oneline -10

From the diff or log, identify:

• What files were added, modified, or deleted
• What features, fixes, or refactors were completed
• Any new dependencies, configurations, or documentation added

Summarize in plain language. Present this summary to the user and ask: "Does this capture today's work, or is there anything to add?" Wait for their response before proceeding.

---

Step 3 — Propose CLAUDE.md updates

Based on the session summary, propose specific updates to CLAUDE.md:

• Update the Current Phase section to reflect what is now complete
• Update the Immediate Next Step — this is the most important line
• Add any new files to the project structure if relevant
• Update any checklist items from ☐ to ✅ if completed today

Show the proposed diff. Ask: "Should I apply these changes to CLAUDE.md?" Wait for confirmation, then write the file.

---

Step 4 — Propose DECISIONS.md entries

Review the session summary for any non-obvious architectural or technical choices made today. For each decision identified, propose a new append-only entry in this format:

### 00N · Decision Title
**Date:** YYYY-MM-DD
**Status:** Finalized

**Decision:** What was chosen.

**Rationale:** Why — the reasoning that would otherwise be lost.

**Rejected alternatives:**
- Option A — why not
- Option B — why not

If no new decisions were made, state that explicitly and skip this step.

Show proposed entries. Ask: "Should I append these to DECISIONS.md?" Wait for confirmation, then write the file.

---

Step 5 — Draft git commit message

Write a conventional commit message in this format:

<type>(scope): short imperative summary (≤72 chars)

- Bullet describing what was done
- Another completed item
- Third item if needed

Next: The single immediate next action

Types: feat, fix, refactor, docs, chore, test, style

Present the commit message. Ask: "Should I run git commit -m ... with this message?"

Stage your files first with git add <files> or git add -p for interactive review. This command will not stage files automatically.

Wait for confirmation before running the commit.

---

Step 6 — Claude.ai memory reminder

Print this reminder block exactly:

─────────────────────────────────────────────
MANUAL STEP REQUIRED — Claude.ai Memory

Claude Code cannot update your Claude.ai memory.
Open Claude.ai and send this message:

"Update your memory: today I completed [X].
Current state of [project] is [Y].
Next step is [Z]."
─────────────────────────────────────────────

Fill in [X], [Y], and [Z] from the session summary before printing.

---

Completion

Print:

✅ Wrap-up complete.
   CLAUDE.md      — updated
   DECISIONS.md   — updated (or: no new entries)
   Git commit     — committed (or: skipped — stage files and commit manually)
   Claude memory  — manual step above
   
   Total ritual: ~5–10 min. See you next session.