verify-review-findingslisted
Install: claude install-skill theonly1me/shadowclone
# Verify Review Findings
## Use when
A pull request has review comments, bot findings, or a list of issues from another agent. A finding is a claim, not a fact. Check each one before you change code or reply.
This skill follows `shadowclone-work` for fixes, commits, pushes, and fix replies. It differs from `shadowclone-work` only in how it declines a finding. A wrong AI finding gets a one-line reply. A human comment is declined only after the user decides.
## Gates
1. Did you read each finding at the head commit of the pull request? A finding about an older commit can be stale.
2. For each finding, do the file and the line exist, and does the code around them do what the finding says? A finding can be right about the problem and wrong about the place.
3. Can you show the claim with a test, a command, or the code itself? If not, label it as not verified.
4. Did you ask what each suggested fix would break, such as a caller, a test, or a documented behavior?
5. Does each finding have a verdict: confirmed, partly right, pre-existing, wrong, stale, or not verified?
6. Did you fix each confirmed finding, reply on its thread with the commit SHA only, and ask the user before you declined a human comment?
## Process
Write in the user's voice. Before you write, read `~/.agents/voice.md`. If it does not exist, build it once from the user's merged pull requests, review comments, and commit messages. Use only text that the user wrote, and name those sources in your handoff. Never o