memory-wrap-up

Perform a session-end review of the vault: verify note quality, update brain/ accumulators, resolve orphans, flag stale thinking/ notes, and commit.

Workflow

1. Gather What Was Done

• Read ${CLAUDE_PROJECT_DIR}/.remember/now.md for session activity buffer
• Scan the conversation for any notes created or modified this session
• Run git status in the vault repo to list all uncommitted or recently changed files

2. Verify Note Quality

For each note created or modified this session, check:

• Frontmatter complete for its tier?
  • Capture tier (inbox/thinking): title, date, tags
  • Curated tier: all above plus confidence, related, source, source-type
• At least one [[wikilink]] present?
• Placed in the correct folder per vault conventions?
• description field present and accurate (if applicable)?

Flag any note that fails a check. Fix automatically when the fix is unambiguous (e.g., missing date). Ask before restructuring content.

3. Update brain/ Accumulators

Check whether this session produced any of the following. If yes, append an entry to the corresponding accumulator file:

Signal	File
A non-obvious architectural or research decision	brain/decisions.md
A reusable pattern or approach	brain/patterns.md
A gotcha, footgun, or hard-won lesson	brain/gotchas.md
A goal shift or reprioritization	brain/goals.md (offer to update, ask first)

Entry format:

- **YYYY-MM-DD**: Brief description. [[link-to-full-note]] (confidence: observed)

Skip the accumulator update if the session produced nothing relevant to that category.

4. Check for Orphans

Find any notes created this session that are not linked from at least one other vault note.

For each orphan:

• If there is an obvious parent (a project note, a related solution), add the wikilink automatically and report it
• If no obvious parent exists, flag it for user input — do not silently leave it orphaned

5. Update brain/index.md

Update the "Recent Context" section with a one-line summary of this session. Format:

- **YYYY-MM-DD**: <one sentence — what was worked on and key outcome>

Keep the section to the 10 most recent entries. Remove the oldest if at capacity.

6. Check thinking/

Scan all notes in thinking/. Determine age from the date field in frontmatter (fall back to file modification time if no frontmatter). For each:

• Age < 3 days: Leave in place, no action
• Age 3–7 days: Flag to user — promote to a proper note or delete?
• Age > 7 days: Recommend deletion unless the user has a specific reason to keep it

Thinking notes are temporary scratch space, not long-term storage.

7. Suggest Improvements

Based on what happened this session, surface one or more of the following if relevant:

• Friction points: something that was awkward or required unnecessary manual steps
• Automation gaps: a recurring pattern that should become a template, hook, or skill
• Missing structure: a topic that appears repeatedly but has no dedicated note or project file

Keep suggestions concrete and actionable. Skip this step if nothing stands out.

8. Commit

Stage only the specific files created or modified during this wrap-up. Do not stage entire folders or use git add -A.

git add <list each file path explicitly>
git commit -m "vault: wrap-up — <one-line session summary>"

If nothing changed in the vault, report that and skip the commit.

Fallback Behavior

Missing	Fallback
.remember/ files	Rely on conversation context and git status only
brain/ files	Skip brain/ accumulator updates; note that /claude-memory:init should be run
01-projects/ empty	Skip project-related checks
thinking/ empty	Skip thinking/ triage
No vault changes this session	Report "nothing to wrap up" and skip commit

Always produce a wrap-up. A partial wrap-up with honest gaps is better than a refusal.

9. Report

End with a structured summary:

• Done: What was captured or confirmed this session
• Fixed: Note quality issues found and resolved
• Updated: brain/ files changed (list which ones)
• Flagged: Items requiring user input (orphans with no clear parent, thinking/ promotions, goal shifts)