verify-review-findings SKILL.md skillA
verify-review-findings from theonly1me/shadowclone is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add theonly1me/shadowclone/verify-review-findings@git:20261018.7be4fabPins git:20261018.7be4fab in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- theonly1me/shadowclone
- Path
skills/verify-review-findings/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261018.7be4fab, committed Oct 18, 2026
- First version recorded
- Oct 4, 2026
- Size
- 6,551 bytes
- Repository stars
- 21
- License
- MIT
Use when a pull request has review comments or bot findings to check or address. Also use it for "are these comments right?", "triage the review", "address the review comments", "check the PR comments", or "check what the bot found". Checks each finding against the code at the head of the pull request, and confirms the file, the line, and the claim. Fixes each confirmed finding without waiting, replies by fixed rules, and reports each verdict. Asks the user before it declines a human comment.…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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? …
Read the whole file at its exact version.
How to install
mdr add theonly1me/shadowclone/verify-review-findings@sha256:9873bf750fc9ea2fThe line at the top of this page pins the label git:20261018.7be4fab, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7eadxbxkzkrevkia)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 4, 2026 and Oct 18, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.7be4fab latest | 2026-10-18 | 7be4fab | 6,551 B | A | view · diff |
| git:20261004.06f281b | 2026-10-04 | 06f281b | 3,925 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6551 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
theonly1me/shadowclone · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7eadxbxkzkrevkia GET https://markdownregistry.com/api/v1/resolve?ref=theonly1me/shadowclone/verify-review-findings GET https://markdownregistry.com/api/v1/blob/9873bf750fc9ea2f062c2f62ce5e8d284ab46ade7bb90cba10a3b1e6f11ab4e5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.