update-stale-docs

To keep documentation fresh after code changes, run a structured checklist that cross-checks ABOUTME tags, inline diff comments, decision docs, memory entries, and README notes to surface inconsistencies before committing.

Finding stale documentation affected by recent commits involves scanning inline diff notes, memory entries, and decision docs to audit current relevance, ensuring a comprehensive doc sweep that highlights inconsistencies for update.

Update ABOUTME tags and memory entries before a commit by performing a cohesive doc sweep that validates their relevance against code changes, prompting necessary refreshes to maintain alignment across all sources.

Run a documentation review sweep for code maintenance immediately after completing a feature, ensuring all impacted docs including README guidance and decision documents are refreshed as part of the same unit of work.

Updating stale docs requires no external dependencies, applying directly to existing workflows that involve code changes and ongoing maintenance across memory, ABOUTME tags, inline diffs, decision docs, and README notes.