review:follow-up SKILL.md skillA
review:follow-up from bendrucker/claude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bendrucker/claude/review:follow-up@git:20261107.21dcb6dPins git:20261107.21dcb6d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bendrucker/claude
- Path
plugins/review/skills/follow-up/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261107.21dcb6d, committed Nov 7, 2026
- First version recorded
- Jul 24, 2026
- Size
- 9,404 bytes
- Repository stars
- 18
- License
- MIT
Follow up as the reviewer on a PR/MR you reviewed: did the author's fixes actually grasp each concern you raised, or just go through the motions? Finds silently resolved or mechanically-fixed threads and returns a graded re-review call. Use when you left review comments and want to verify the author acted on them before re-approving. Triggers: "did they fix my review comments", "re-review this PR", "check whether the author addressed my feedback".
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
# Review Follow-Up Follow up on my review of: $ARGUMENTS You are the reviewer. The question is not "did the author reply?" but "did the fix actually grasp each concern, or go through the motions?" Status is a signal. The code is the verdict. Report any mismatch between the two (resolved but not fixed, unresolved but fixed) as a finding. All diff and file reading happens in Explore sub-agents. Your main session holds only the structured verdicts they return, never raw diffs, keeping my development context free. ## Context - Remote URL: !`git remote get-url origin 2>/dev/null || echo "unavailable"` - Branch: !`git branch --show-current 2>/dev/null || echo "unavailable"` ## Workflow ### Resolve Target If `$ARGUMENTS` carries a URL or identifier, use it. If it's empty, detect the current branch's open PR/MR. Pick the platform from `git remote get-url origin`, then: - GitHub: `gh pr view --json url,state --jq '.url'` - GitLab: `glab mr view --output json | jq -r '.web_url'` …
Read the whole file at its exact version.
How to install
mdr add bendrucker/claude/review:follow-up@sha256:968182f22828bf1aThe line at the top of this page pins the label git:20261107.21dcb6d, 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_n7hhvrbrgmwsekrd)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jul 24, 2026 and Nov 7, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261107.21dcb6d latest | 2026-11-07 | 21dcb6d | 9,404 B | A | view · diff |
| git:20261018.ea39d1d | 2026-10-18 | ea39d1d | 9,345 B | A | view · diff |
| git:20260902.42e53f9 | 2026-09-02 | 42e53f9 | 9,312 B | A | view · diff |
| git:20260902.80b1277 | 2026-09-02 | 80b1277 | 9,281 B | A | view · diff |
| git:20260727.14c22cf | 2026-07-27 | 14c22cf | 9,190 B | A | view · diff |
| git:20260725.c2280fd | 2026-07-25 | c2280fd | 11,320 B | A | view · diff |
| git:20260724.2913803 | 2026-07-24 | 2913803 | 11,914 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 (9404 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
bendrucker/claude · 18 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n7hhvrbrgmwsekrd GET https://markdownregistry.com/api/v1/resolve?ref=bendrucker/claude/review:follow-up GET https://markdownregistry.com/api/v1/blob/968182f22828bf1a2e5b948c0e7f19b528704692e12a1fa9daebbd5e037aafcd
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.