---
title: "Read and act on a finding | Proofline Help"
description: "A finding connects a code change to a failure mechanism and the evidence that supports it. Verify that explanation before changing the code."
url: https://proofline.sh/help/findings/
---

[Help center](/help/)

# Read and act on a finding

A finding connects a code change to a failure mechanism and the evidence that supports it. Verify that explanation before changing the code.

[![A database capacity finding on its own page: the cited Terraform lines, Impact, Recommended action, a reply on the pull request and the Confirm, Dismiss, Mark fixed and Accept risk buttons, in the fictional Northstar Demo workspace.](/help-images/finding-light.png)](/help-images/finding-light.png)

Open a finding to read its impact, evidence, and remediation. Fictional demo workspace.

## Inspect the explanation

1.  Open the finding from its review.
2.  Read the affected code and the failure mechanism.
3.  Inspect the supporting evidence and its environment.
4.  Compare the suggested correction with your intended deployment behavior.

Read the claim from its title into the text beneath it. The title contains the first sentence; **Impact** shows the failure path one step per line when the reviewer supplied a chain.

Check the severity above the title. When **Evidence** is available, expand it to read the supporting explanation, or expand **Sources** to inspect the cited references.

When the same finding appeared in the author’s local review of the same change, select **Local finding** to inspect that earlier occurrence. Its date identifies the local review. The link does not mean the pull-request finding has been resolved.

The finding shows its available fix actions beside **Recommended action** and its assessment controls below the thread. If the finding has a linked GitHub comment, select **GitHub comment** above the title to open its discussion. Sections such as **Follow-ups**, **Feedback** and **Fixes** appear only when something is recorded.

## Use the fix prompt

For eligible environment findings, **Copy fix prompt** carries the code references and reviewed commit into a coding agent. [Open a finding's fix prompt in your coding agent](/help/launch-finding-fix-prompt/).

## Inspect follow-ups and comment placement

**Follow-ups** shows recorded answers and their evidence. Publication and GitHub thread activity are recorded separately. [Check a finding's follow-ups and post it to the pull request](/help/publish-finding-followups/).

## Verify the correction

**Mark fixed** records a person's assessment. A new verification result tells you what Proofline established about the changed code. [Verify a correction after marking a finding fixed](/help/verify-finding-correction/).

## More tasks

-   [Read execution evidence for a finding](/help/inspect-finding-execution/)
-   [Check a finding's re-verification at a later commit](/help/inspect-finding-reverification/)
-   [Review a coding agent's fix attempts](/help/inspect-agent-fix-loop/)
-   [Trace a pull request finding to an earlier local review](/help/trace-local-finding/)
-   [Check the evidence behind a finding follow-up](/help/check-finding-answer-evidence/)
-   [Find which findings a combined fix includes](/help/inspect-combined-fix/)

[Check what evidence a review shares](/help/review-data-sharing-and-evidence/).

## Related guides

-   [Read a review](/help/read-review/)
-   [Rerun, stop, or publish a review](/help/rerun-review/)
-   [Set up a coding agent](/help/coding-agents/)
-   [Start a cloud coding-agent session](/help/cloud-coding-agents/)
-   [See feedback on a repository's findings](/help/repository-feedback/)
