Skip to content
BENIBIX Learn

ReportFindings Tool

AI⌨️ Claude CodeBuilt-in Tools

Also known as ReportFindings, Code review findings

The tool that hands back code review findings as a list.

Think of it like

It is like a teacher's list of mistakes, one line for each.

Example

Jack runs a review on his change. Each problem comes back as one row with the file, the issue and what would break.

Why it matters

A list of findings is easy to read, sort and fix one at a time.

Definition

The ReportFindings tool hands back what a code review found as a neat list. Claude Code can then show it in a clear layout, not as plain text. Each finding names a file, a one-line summary and what would go wrong. A finding can also carry a short label, such as correctness or test-coverage. Claude calls it when the review's own steps ask for it.
ReportFindings lists each problem a review found.

Common mistake

Expecting it in every review. Claude only uses it when the review's steps say so.

Key takeaways

  1. 1
    One row each. File, summary, failure.
  2. 2
    Shown neatly. Not as plain text.
  3. 3
    Optional label. Such as correctness.

Learn it properly