update-primary-doc

To synchronize primary documents with repository changes, configure sync rules in CLAUDE.md and run the custom-git-commit workflow. The process matches changed files to patterns and proposes updates automatically.

Table-driven sync rules are configurations read from CLAUDE.md that drive document updates without project-specific hardcoding. They define patterns matching changed files to relevant sections in your primary documents.

Yes, it supports modular primary documents containing a primary file and modules. It propagates changes across related files by reading CLAUDE.md to extract the Primary Document and Sync Rules.

No, it proposes updates rather than applying them directly. It validates documents and stages proposals for safe review, enabling an approval workflow before changes are committed.

You can extend functionality with project-specific child skills like java-update-design or skills-update-readme. These optional skills handle specialized workflows while the primary skill manages generic synchronization.

Updates require correctly configured CLAUDE.md rules extracting the Primary Document, Sync Rules, and Milestones. Without matching changed files to defined patterns, no proposals will be generated or validated.