update-docs

Documentation drift is detected by comparing the live codebase state against existing documentation sections to find inconsistencies. This process identifies where docs no longer mirror the real project structure.

You can automatically update a README by running an analysis that checks app inventory, workflows, and system configurations against current code. It then guides selective content edits to synchronize the documentation.

The best way to synchronize documentation is using live code analysis to enforce consistent, validated updates. This approach ensures docs accurately reflect the current codebase structure and system configurations.

Yes, you can selectively update outdated sections by targeting specific edits that synchronize docs with the current project status. This avoids rewriting entire files and focuses only on drifted content.

Yes, documentation sync works for complex codebases by handling checks across app inventory, workflows, agents, and system configurations. It ensures accuracy regardless of project complexity.

You should avoid automated drift detection when the codebase is rapidly changing mid-development and docs are intentionally deferred. It is best suited for enforcing consistency once project components stabilize.