fact-checker

To verify agent claims about code content, you cross-check the cited file location against the actual repository state. This fact-checking process reads the target file and surrounding context to confirm whether the claim matches the existing code.

Validating state claims requires comparing actions taken via git diff against the repository history. This auditing process checks the diff history to confirm whether code changes occurred exactly as claimed by the subagent.

Detecting hallucinations in subagent code claims involves cross-checking assertions with the repository state. By evaluating content and state claims against the actual file content and git diffs, you produce a verdict with supporting evidence.

Yes, you can check a specific line-level fact by reading the cited file location and analyzing the surrounding context. This content claims verification confirms whether the exact code matches the actual repository content.

Yes, fact-checking code claims requires access to the project workspace, the target file, and the diff history. This environment access is necessary to evaluate claims accurately and produce a verdict with supporting evidence.