session-recap

To update documentation after a coding session, review code diffs and discuss learnings to identify changes, then validate the summary before applying updates to canonical memory logs and domain docs.

Capturing architectural decisions and learnings involves a four-step workflow: diff review, learnings discussion, user validation, and documentation updates to record what changed and why it happened.

Updating CLAUDE.md works by scanning session diffs, extracting code logic changes and user preferences, and outputting canonical memory entries with recommendations to update related domain docs.

Yes, the workflow enforces user validation by presenting a summary of session changes and learnings for your confirmation before any documentation updates are applied.

You need to capture session learnings into canonical memory entries at the end of a coding session to preserve architectural decisions, code changes, and process improvements for future work.

Yes, the session recap workflow operates independently without external dependencies or components, directly reviewing diffs and updating your project documentation files.