doc-sync

Documentation drift is detected by running an automated audit that identifies discrepancies between your codebase and documentation. You can execute a dry run to check the entire project or use incremental checks to spot inconsistencies early.

Synchronization supports code-to-docs, docs-to-code, and full bidirectional reconciliation. This configurable sync ensures you can update API documentation to match code changes or align code with existing documentation.

The best way to fix outdated API documentation is through automated fixing, which orchestrates tools to resolve inconsistencies with user confirmation. This ensures documentation accurately reflects the latest code changes without manual intervention.

Scoped audits are supported alongside incremental checks for documentation synchronization. This allows you to target specific sections of your project rather than scanning the entire codebase, optimizing the drift detection process.

Claims verification works by validating technical claims within documentation against the actual codebase during reconciliation. This traceability check ensures documented behaviors and API endpoints match the implemented logic before completing the sync.

Automated drift detection requires user confirmation before applying fixes to prevent unwanted modifications. While it supports parallel dispatch and iterative refinement, complex semantic mismatches may still require manual review.