doc-sync-enforcer

To keep documentation in sync with code changes, you can analyze staged file modifications and categorize them to prompt necessary updates. This ensures API routes, components, design tokens, and utilities are accurately reflected in docs before a commit.

Documentation synchronization for API routes and components is the process of validating code updates against project documentation files. It maintains documentation integrity by enforcing updates to specs and readmes whenever relevant code is modified.

To validate code updates against FINAL_SPEC.md and README.md, enforce documentation checks that categorize staged file modifications. This process alerts you to necessary documentation updates, preventing inconsistencies between the codebase and your specs.

Yes, you can automate documentation checks for design tokens and utilities by analyzing staged file modifications. This verifies that changes to these elements are accurately reflected in relevant documentation files like CLAUDE.md.

Project documentation becomes outdated after modifying an API route because code changes are often committed without corresponding doc updates. Enforcing documentation synchronization alerts you to update specs and readmes, preventing these inconsistencies.