doc-review

To detect documentation drift after merging code, review the documentation in your pull request against the current codebase and GitHub state to identify discrepancies and ensure technical accuracy.

The best way to check documentation accuracy against a codebase is to cross-reference claims in technical docs with the actual code and GitHub state, flagging any misaligned or outdated information for correction.

To consolidate duplicated information across technical documentation, pinpoint redundant content and recommend a single source of truth, proposing edits that minimize duplication while maintaining alignment with code and design pillars.

Yes, you can validate documentation updates directly within a pull request workflow by reviewing the changed docs for correctness, alignment with GitHub state, and minimal duplication before the merge is finalized.

Project documentation shows inconsistencies with the current code when technical docs are not updated alongside code changes, causing drift between documented features and actual implementation over time.

Automated documentation review for code alignment is limited to proposing edits based on code, GitHub state, and design pillars, requiring human oversight to validate contextual accuracy and approve the recommended single source of truth.