sync-check

To check CLI documentation synchronization, scan your git diff to identify impacted files and report mismatches. This sync-check process prevents drift between code changes and downstream references during refactors or new command additions.

The best way to prevent documentation drift during CLI refactors is to scan git diffs for impacted files. A sync-check verifies downstream references and reports mismatches, providing remediation guidance to improve release quality.

Yes, sync-check works with standard git diffs. It detects code changes via the git diff, maps impacted skill and SOP files, and verifies downstream references to ensure documentation remains consistent across artifacts.

To verify downstream references during a code review, run a synchronization check on your recent changes. It identifies out-of-sync items across your CLI documentation and provides a ready-to-run action to re-align docs.

You need to run a documentation consistency check during developer workflows involving refactors, new commands, or docs updates. This ensures downstream artifacts remain synchronized and prevents inconsistent references across CLIs.