update-project-docs

To automatically update project documentation, run a session review that checks git diff, captures new learnings, and refreshes CLAUDE.md and MEMORY.md to keep your project docs current and coherent.

The best way to capture architecture decisions is to review session changes via git diff and append the new learnings, patterns, and decisions directly into your project's CLAUDE.md and MEMORY.md files.

Memory management works by enforcing a 200-line limit on MEMORY.md, moving detailed notes into separate topic files when the limit is reached to prevent memory drift and maintain coherent project documentation.

Yes, you can use this to review git diff for ongoing project work, identifying what changed to inform targeted updates to CLAUDE.md and MEMORY.md while applying explicit rules to avoid duplication.

To prevent duplication when updating CLAUDE.md and MEMORY.md, the process applies explicit deduplication rules during the targeted doc updates, ensuring new learnings are added without repeating existing content.