Product Coherence

To audit README documentation against a codebase, compare documented claims with actual code exports and entry points to detect ghost features, naming drift, and undocumented capabilities. The audit generates source references and remediation guidance.

Documentation drift in public APIs occurs when implemented features diverge from documented claims over time. Auditing README.md, docs/, and CHANGELOG.md files against the actual codebase surfaces these undocumented capabilities and naming inconsistencies.

You can check CHANGELOG accuracy by running an audit that maps claims to actual code exports and entry points. This process identifies misalignment between marketing promises and shipped features, providing traceable mappings for remediation.

Yes, this audit applies to the docs/ folder, README.md, and CHANGELOG.md to identify undocumented capabilities. It compares documentation against the codebase to surface gaps and provides recommended fixes with source references.

The best way to fix naming drift is to audit documentation against the codebase to identify inconsistencies. The audit maps claims to actual code exports and entry points, providing organized findings with recommended fixes.

Yes, this documentation audit works without external dependencies. It analyzes your codebase and documentation files directly to detect misalignment, ghost features, and naming drift, generating traceable mappings and remediation guidance.