pull-feedback SKILL.md skillA
pull-feedback from technicalpickles/pickled-claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add technicalpickles/pickled-claude-plugins/pull-feedback@git:20260923.5563fd5Pins git:20260923.5563fd5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- technicalpickles/pickled-claude-plugins
- Path
plugins/git/skills/pull-feedback/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260923.5563fd5, committed Sep 23, 2026
- First version recorded
- Apr 20, 2026
- Size
- 6,067 bytes
- Repository stars
- 12
- License
- MIT
Use when the user has authored a GitHub pull request and wants to work through review feedback on it. Triggers on phrases like "pull down the review on #N", "address the feedback", "what did @reviewer say on my PR", "let's work through the comments", or any request to triage, respond to, or systematically handle review threads on the user's own PR. Do NOT use for reviewing someone else's PR, authoring PR content or replies, or checking which PRs are waiting on the user for review.
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
# Git Pull Feedback ## Overview Pulls review feedback on a PR the user authored into a working doc with per-thread triage slots. The point is rigor: every unresolved thread gets a tentative verdict (valid / invalid / nice-to-have / needs-clarification) with reasoning and a plan, so the user can work through feedback deliberately instead of rubber-stamping. **Announce:** "Using git:pull-feedback to pull and triage feedback on PR #N." ## Workflow ### 1. Fetch ```bash ./fetch.sh [ref] ``` `ref` accepts a bare number, `#N`, `owner/repo#N`, a PR URL, or nothing (auto-detects from current branch). The script writes a skeleton doc to `.scratch/pr-reviews/<N>/threads.md` with `_pending triage_` placeholders and prints counts on stdout. Use this output location — don't invent your own filename. ### 2. Orient only if context is cold Add a `## Summary` section (1-2 sentences on what the PR does + state of the review) **only if** you don't already know the PR. If the user has been discussing it in conversation or the branch name tells you, skip — guessing wastes tokens and risks confabulation. ### 3. Triage each unresolved thread (shallow pass) …
Read the whole file at its exact version.
How to install
mdr add technicalpickles/pickled-claude-plugins/pull-feedback@sha256:16da19cdb62ecd30The line at the top of this page pins the label git:20260923.5563fd5, 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_vo6zgbrwyjwha57b)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 20, 2026 and Sep 23, 2026, about one every 78 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.5563fd5 latest | 2026-09-23 | 5563fd5 | 6,067 B | A | view · diff |
| git:20260908.7f6ad88 | 2026-09-08 | 7f6ad88 | 6,062 B | A | view · diff |
| git:20260420.6eee650 | 2026-04-20 | 6eee650 | 5,831 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 (6067 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
technicalpickles/pickled-claude-plugins · 12 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vo6zgbrwyjwha57b GET https://markdownregistry.com/api/v1/resolve?ref=technicalpickles/pickled-claude-plugins/pull-feedback GET https://markdownregistry.com/api/v1/blob/16da19cdb62ecd30a23335f6e43ddd042c095c466accea50a50475d7baddabdf
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.