docs-sync-checker

To detect documentation drift, compare filesystem-discovered tools with README and docs entries. This process surfaces missing entries, stale references, and version mismatches across skills, agents, and commands using deterministic reporting.

Yes, you can fail CI/CD builds on documentation drift by running the sync checker in strict mode. It generates machine-readable JSON output and actionable remediation guidance for missing or stale entries.

Checking YAML frontmatter against markdown README files involves parsing metadata and cross-referencing it with filesystem definitions. This surfaces inconsistencies across skills, agents, and commands during a deterministic scan.

The best way to find missing entries in docs is running a 4-phase workflow: Scan, Cross-Reference, Detect, and Report. It compares filesystem definitions with documentation to generate precise fixes for missing and stale entries.

Yes, the documentation sync checker supports machine-readable JSON output for CI/CD integration. It applies deterministic reporting to produce actionable issues for version mismatches and documentation drift.

Stale entries in your README occur when filesystem definitions and documentation drift apart. Running a sync checker cross-references markdown tables and lists with actual files to detect and report these inconsistencies.