git-pr-feedback SKILL.md skillA
git-pr-feedback from ivy00johns/skill-madness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ivy00johns/skill-madness/git-pr-feedback@v1.4.0Pins v1.4.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ivy00johns/skill-madness
- Path
skills/git/git-pr-feedback/SKILL.md- Versions recorded
- 5
- Latest version
- v1.4.0, committed Oct 8, 2026
- First version recorded
- May 1, 2026
- Size
- 7,663 bytes
- Repository stars
- 11
- License
- MIT
Fetch, triage, and address PR review comments from GitHub Copilot and human reviewers. Use when the user asks to check PR feedback, review comments, address reviewer suggestions, or fix PR issues. Trigger on: "check PR comments", "what did copilot say", "address PR feedback", "fix review comments", "handle PR suggestions", "review feedback", "PR comments", "copilot review", "reviewer feedback", or any mention of responding to pull request comments. Also trigger when the user returns to a PR…
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
# PR Feedback Handler
Fetch review comments on a GitHub PR, triage them, fix what's clear, ask about
what's ambiguous, and reply to each comment on GitHub with what was done.
## Workflow
### 1. Identify the PR
Determine the PR number from context:
```bash
# Current branch's PR
gh pr view --json number -q .number
# Or from a URL the user provided
# Or from a specific PR number they mentioned
```
### 2. Fetch All Comments
Pull both review comments (inline on code) and issue-level comments:
```bash
# Inline review comments (from Copilot and reviewers)
gh api --paginate repos/{owner}/{repo}/pulls/{pr}/comments
# General PR comments (not on specific lines)
gh api --paginate repos/{owner}/{repo}/issues/{pr}/comments
# Review summaries
gh api --paginate repos/{owner}/{repo}/pulls/{pr}/reviews
```
Use `--paginate` to ensure all comments are returned — the default page size
is 30, which can silently miss comments on large PRs.
Parse each comment to extract:
- **who**: `user.login` — distinguish `Copilot`, `copilot-pull-request-reviewer[bot]`, and human reviewers
- **where**: `path` and `line` — the file and line the comment targets
- **what**: `body` — the feedback text
…Read the whole file at its exact version.
How to install
mdr add ivy00johns/skill-madness/git-pr-feedback@sha256:01ab34c9b8788e63The line at the top of this page pins the label v1.4.0, 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_gtkzmrymstpjeq2m)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 1, 2026 and Oct 8, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.4.0 latest | 2026-10-08 | d1d8537 | 7,663 B | A | view · diff |
| v1.3.0 | 2026-06-22 | d646b00 | 6,784 B | A | view · diff |
| v1.3.0 | 2026-05-20 | bc9aa5a | 6,773 B | A | view · diff |
| v1.2.0 | 2026-05-20 | 63b19b5 | 6,747 B | A | view · diff |
| v1.2.0 | 2026-05-01 | 2990900 | 6,747 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 (7663 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
ivy00johns/skill-madness · 11 stars · license MIT · pushed 2026-10-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gtkzmrymstpjeq2m GET https://markdownregistry.com/api/v1/resolve?ref=ivy00johns/skill-madness/git-pr-feedback GET https://markdownregistry.com/api/v1/blob/01ab34c9b8788e63ccdb5c2f8dc2accf17db548fc8dc597f587a42be1b407c31
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.