doc-sync-playbook

Synchronize CLAUDE.md with .claude/rules/*.md using git-diff analysis.

1|Updated Mar 6, 2026

Search Tags:#documentation #claude.md #sync #rules #git-diff #serena-mcp

Ready to run

npx skills add https://github.com/zenbuapps/zenbu-powers --skill doc-sync-playbook

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-sync-playbook
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/doc-sync-playbook
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill doc-sync-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation synchronization between CLAUDE.md and the rules under .claude/rules to ensure changes are captured without disrupting existing content.

Core Features & Use Cases

Analyze git diffs to identify relevant documentation updates.
Compare against existing CLAUDE.md and rules to apply only necessary changes.
Coordinate with Serena MCP to map code changes to documentation updates.

Quick Start

Run the doc-sync-playbook on a repository with recent changes to automatically synchronize CLAUDE.md and .claude/rules/*.md.

Frequently Asked Questions about doc-sync-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sync CLAUDE.md with rules files after a git commit?▼

To sync CLAUDE.md with rules files, this playbook analyzes your git diffs to identify code changes and selectively updates CLAUDE.md and .claude/rules/*.md to reflect new architecture and guidance while preserving existing correct content.

What is the best way to keep documentation updated during a project refactor?▼

Keeping documentation updated during a refactor requires mapping code changes to documentation updates. This playbook coordinates with Serena MCP to analyze git-diffs and apply only necessary documentation changes without disrupting existing correct content.

Does doc-sync-playbook work with Serena MCP and standard Git workflows?▼

Yes, the doc-sync-playbook is specifically designed for projects using Serena MCP and Git workflows. It leverages git-diff analysis to map code changes to the necessary documentation updates in CLAUDE.md and .claude/rules/*.md.

Can I update documentation selectively without overwriting existing correct content?▼

Yes, you can update documentation selectively. The playbook compares your git changes against existing CLAUDE.md and rules to apply only necessary updates, ensuring it preserves existing correct content while adding required guidance.

How does git-diff analysis map code changes to documentation updates?▼

Git-diff analysis maps code changes to documentation updates by identifying modified files in your repository and coordinating with Serena MCP to determine which sections of CLAUDE.md and .claude/rules/*.md require synchronization.

When should I not use automated documentation syncing for feature development?▼

You should avoid automated documentation syncing when your repository lacks recent git changes or when your project does not use Serena MCP and .claude/rules/*.md structures, as the playbook relies on these to map updates.