documentation-verify

To verify documentation accuracy, cross-reference claims, CLI commands, and API signatures against source code. This process flags unsupported or outdated claims to prevent incorrect information from misleading users.

Verifying API signatures involves cross-referencing documented claims with actual source code to identify incorrect statements. It categorizes documentation issues like unsupported features or outdated information to ensure technical writing accuracy.

Yes, documentation verification requires git diff for changed files and full codebase access to validate code-docs consistency. This access allows the process to accurately cross-reference claims against actual source code.

To validate updated CLI commands, run a verification check against the codebase to ensure help text and usage examples are updated accordingly. This flags any outdated arguments or incorrect statements in technical writing.

Documentation shows unsupported features when technical writing is not updated after code changes. Cross-referencing documentation claims against source code during code review identifies and flags these outdated or incorrect statements for correction.