Docs / More
Findings
Unused exports, duplicate implementations and wrappers. A finding closes only when a re-scan drops its fingerprint.
A finding stays open until the graph says it is gone. An edit is not enough.
Findings are concrete issues from the last index: unused exports, two files exporting the same implementation, and wrapper functions that only call another export.
To fix one, ask your agent in chat. Prism does not mark it resolved because something was edited. It re-runs the report. If the fingerprint is still there, the finding stays open.
prism findings list
prism findings mute a3f8c5f0c392dbebMute lives in gitignored {repo}/.prism/. It is not a markdown file and it
is not committed.
The loop
list_findings → your agent edits → this repo’s checks
↑ │
└──── re-scan; fingerprint gone? ────┘| Step | Rule |
|---|---|
| Fix | Ask in chat. The brief is “fix this finding only.” |
| Verify | The stop hook runs the checks this repo actually has. None → —, not Failure. |
| Resolve | Only a re-scan that drops the fingerprint. An edit is not resolve. |
The open finding count does not move because a file was edited; only a re-scan changes it.
Kinds
| Source | What it is |
|---|---|
| unused-export | An export nothing in the index imports |
| duplicate-implementation | Two files exporting the same name / body |
| wrapper-over-existing | A function whose whole body is one call to another export |
Muted findings stay out of the default list. includeMuted shows them.
When this is wrong
- Reviewing a PR never fixes a finding on its own. Fix one only if you asked.
- A Python-only or lint-only repo must not fail a fix when checks are —. The re-scan still runs.
- Mute is local and gitignored. It does not travel with the repo.