Interpret findings and navigate the diff

PR reviews and local reviews share one surface: a file tree on the left, a diff viewer in the center, and the Review tab on the right. This page explains how to read and act on what Kensa produces there.

Read a finding

Each finding card shows:

• Severity — critical, major, minor, or info, with critical the most urgent.
• Attribution — the agent and provider/model that produced the finding; after consolidation, agreement across providers is a confidence signal.
• Location — a file:line link that opens the file in the diff at that line.
• Detail and fixes — expandable Why? and Verification steps sections, a suggested-code block when offered, and a Fix prompt button that copies a ready-to-paste instruction for your coding agent.

Findings group by file. Severity pills and agent chips above the list filter it, and a consolidator has already deduplicated overlapping findings across agents.

Triage before you act

• Keep includes a finding in the review; Skip excludes it. Skipped findings stay skipped on later reviews of the same PR.
• The publish button counts the findings it will post, so triage first.

Navigate the diff

• Files Changed lists every changed file with its +/- counts and badges for AI findings and human review threads; a Referenced section lists files outside the diff that findings point at.
• View modes: File (whole file), Hunk (changed hunks only), Inline (+/- inline), and Split (side-by-side), plus Words for word-level highlighting in Hunk and Inline. Files outside the diff open in File mode only.
• Overlay chips in the diff header toggle AI findings, human threads, and resolved threads.

Publish and export (PR reviews)

• Publish … to your provider posts the kept findings as a pending review on the PR. Publishing without triage posts all findings after a confirmation.
• Later publishes add only new comments; published findings can be resolved or re-published from their cards.
• Export copies the review for use elsewhere. Local reviews have no Publish action.

If something goes wrong

• A pending review blocks publish — use Dismiss & retry, or resolve the pending review on the provider.
• Publish fails — the button offers a retry; findings already posted are not duplicated.
• The PR is merged or closed — publishing and resolving are disabled and the surface becomes read-only.

Next step

Source Control and worktrees