fact-check

Verifying factual claims in documentation against the codebase and git history requires cross-referencing document statements with source code and git logs. This process applies to auditing reports, plans, and documentation for accuracy in quantitative data, naming conventions, and behavioral descriptions.

Automatically fixing factual errors in numbers and names directly within a report is supported through in-place correction. This functionality edits the document directly to correct inaccuracies in quantitative data and naming conventions based on codebase verification.

Auditing project recap reports for commit hash and file count accuracy is best handled by verifying mentioned commit hashes, file counts, and feature descriptions against the repository's actual state. This ensures that quantitative data and temporal information match the git history.

Documentation fact-checking works with standard file reading and bash commands for git operations by requiring tools for reading files, globbing, grepping, editing, and executing bash commands. These tools enable file analysis and git history verification within the codebase.

Generating a summary of confirmed, corrected, and unverifiable claims after a report audit is achieved through automated reporting. This functionality produces a clear verification summary detailing which factual claims match the codebase and which were corrected.