mp-update-docs

To keep Claude Code documentation in sync, you can scan your markdown inventory, analyze recent git diffs and project context, then apply targeted edits to instruction files and READMEs to eliminate documentation drift.

Documentation drift happens when instruction markdown files become outdated as scripts and conventions change. You fix it by scanning project context and recent git activity to propose targeted edits per file, updating only the documentation.

You can automatically update README files by pulling recent git activity and project signals like package.json to identify mismatches, generating a per-file update plan, and applying the approved changes directly to the markdown files.

Yes, recent Claude conversation history is analyzed alongside project files and git context to detect outdated sections, missing patterns, and mismatches, ensuring documentation reflects actual current workflows.

It produces a per-file update plan and asks which changes to apply, ensuring manual review. After approval, it edits only documentation files and can optionally commit the synchronized result directly.

You should avoid automated synchronization when you need to edit source code alongside documentation, as this workflow strictly edits only markdown files and does not modify scripts, tools, or other project conventions.