Find documentation vs code drift

Detect documentation and code-comment drift via adversarial review

Finding documentation and comments that have drifted from current code before releases or after large refactors.

• · git repo (implicit cwd)

• · ranked markdown drift report
• · doc findings: concrete claims vs code (verified, contradicted, stale)
• · comment findings: stale/redundant comments per code cluster
• · prioritized recommendations

• · git CLI (file enumeration, blame history)
• · bash grep/sed for file discovery
• · parallel agent fleet (review clusters, adversarial verify)

• · git repo initialized with tracked docs
• · non-test Go files present
• · git history available for blame/age analysis

• · No tracked docs found → report is comment-only
• · Agent review times out on large code cluster → finding skipped (non-fatal)
• · Adversarial verify rejects finding → finding demoted or rejected (conservative)
• · Comment language ambiguous → agent flags as uncertain, ranked lower

• · Adversarial verify phase challenges each finding before ranking (anti-false-positive)
• · Ranked report (highest drift severity first) guides prioritization
• · Read-only design: produces report, never edits
• · Comment staleness detected via code cluster analysis + temporal patterns