wrap-up

Session Wrap-Up

Review the current session's work and update all relevant documentation before committing.

Steps

1. Gather Session Context

Collect what changed this session:

git diff --name-only HEAD  # unstaged + staged changes vs last commit
git diff --cached --name-only  # staged changes only

1b. Mine Commit Messages for Un-Captured Learnings

Check this session's commits for discovery signals that may not have been recorded:

# Get session start timestamp (check per-session file first, then legacy shared file)
SESSION_DIR={session-dir}
SESSION_START=$(ls -t "$SESSION_DIR"/.sessions/*.start 2>/dev/null | head -1 | xargs cat 2>/dev/null)
if [ -z "$SESSION_START" ]; then
    SESSION_START=$(cat "$SESSION_DIR/.session-start" 2>/dev/null)
fi
# List commits made this session
git log --since="@${SESSION_START}" --format='%h %s' 2>/dev/null

Scan commit subjects for learning signal words: fix, discover, gotcha, quirk, workaround, bug, edge case, actually, found that, regression, broken, issue.

For each flagged commit:

1. Check if the topic already appears in the learnings file
2. If not, flag it as a potential un-captured learning

Report flagged commits (if any) before proceeding to step 2:

Potential un-captured learnings from commits:
- abc1234: "fix: Verify FriendlyName rejects 5+ digits" -- not found in learnings

Skip this step if no commits were made this session or none match signal words.

2. Capture Learnings

Review the session's changes and identify anything worth recording:

• Debugging insights or root causes discovered
• API quirks or gotchas encountered
• Patterns that worked (or didn't)
• Configuration pitfalls

Add entries to .claude/learnings.md using the standard format:

## [YYYY-MM-DD] Topic

**Discoveries:**

1. **Finding**: What was learned
   - Context and details

If a learning is stable and broadly applicable, promote it directly to the target doc (CLAUDE.md, design docs, etc.) and note "Promoted to: [target]" in the learnings entry.