audit-docs

Auditing architecture documentation against a codebase is done by sequentially discovering docs, comparing them to implementation, and generating discrepancy reports. This automated process identifies documentation drift and prompts for user approval on fixes.

Documentation drift occurs when code changes are not reflected in docs. You catch it by running sequential audits that compare architecture documents against implementation, generating detailed findings of discrepancies and verified accurate sections.

Yes, you can resume an interrupted audit because the process uses file-based checkpointing to save progress. This resumption capability allows the sequential documentation auditing to continue after interruptions without restarting.

Yes, the audit generates a detailed summary of findings after auditing architecture documents against the codebase. It creates reports of discrepancies and verified accurate sections, then prompts for user approval on fixes.

The best way to ensure documentation accuracy and consistency is regular automated auditing that discovers architecture documents, compares them against implementation, and generates discrepancy reports with summaries to prompt user-approved fixes.

No external dependencies are required to run a documentation consistency audit. The process orchestrates session initialization, auditing, summarizing, and optional verification phases using self-contained scripts and references.