semi-formal-code-review

To generate an evidence-backed code review, provide a PR diff and the agent analyzes changed implementations to produce structured findings with concrete file:line citations. It traces callers, data flows, and tests to flag un-tested paths.

Evidence-first code review is a structured assessment requiring concrete file:line citations for all findings. It traces important callers and callees for changed code paths and inspects relevant tests to verify coverage and identify gaps.

Yes, you can use static analysis on a codebase patch to find un-tested paths. The agent inspects relevant tests to verify coverage, reading the changed implementations rather than just diff summaries to flag testing gaps.

Traceability in code review helps with diff analysis across codebases by ensuring all findings cite concrete evidence. It applies structured reviews to PRs, diffs, and patches, tracing data flows and callers to validate changes.

The best way to verify test coverage for changed code paths is inspecting relevant tests alongside tracing callers and callees. This evidence-first approach flags un-tested paths and gaps by reading the actual changed implementations.

Your code review lacks traceable findings when it relies on diff summaries instead of reading changed implementations. Applying evidence-first reviews with concrete file:line citations ensures all findings trace callers, data flows, and tests.