doc-syncer

Documentation synchronization automates updates to technical docs, design decisions, and feature readmes when code changes occur. The Skill reads your doc registry and sync rules, identifies affected sections, updates them precisely, validates links and versions, and provides a completion report—eliminating manual alignment work.

Sync documentation when features are completed, data structures are modified, KPIs are updated, or APIs are refactored. Synchronization keeps technical design, decision records, and feature readmes aligned with evolving code, reducing inconsistency risk and maintenance overhead.

The Skill analyzes your change scope, reads existing documentation context, updates precise document sections while preserving structure and versioning, automatically validates links and references, and generates an update summary for quick review before completion.

Yes. Markdown documentation can be automated through sync rules that define update patterns. The Skill processes frontmatter metadata, maintains document structure integrity, and ensures consistent versioning across linked technical documentation after code modifications.

Synchronization works with markdown-based documentation including technical design docs, decision records, feature readmes, and docs with frontmatter metadata. It maintains reference consistency, version alignment, and link validity across your documentation registry.

The Skill automatically validates links and versioning during the sync process, detecting and flagging inconsistencies before completion. This prevents broken references and misaligned version numbers, ensuring documentation integrity across all affected sections.