Agent skill · Code Review & Quality

fetch-pr-feedback

Fetch unresolved review comments from a PR and evaluate with receive-feedback skill

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill fetch-pr-feedback --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/analysis/fetch-pr-feedback/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Fetch PR Feedback Fetch review comments from all reviewers on the current PR, format them, and evaluate using the receive-feedback skill. Excludes the PR author and current user by default. Line-specific comments belonging to resolved review threads are also excluded by default. ## Usage ```bash /beagle-core:fetch-pr-feedback [--pr <number>] [--include-author] [--include-resolved] ``` **Flags:** - `--pr <number>` - PR number to target (default: current branch's PR) - `--include-author` - Include PR author's own comments (default: excluded) - `--include-resolved` - Include line-specific comments from resolved review threads (default: excluded) ## Instructions ### Gates (sequence; do not skip) Advance only after each **Pass when** is satisfied. 1. **PR context** — **Pass when:** `$PR_NUMBER` is set to a positive integer and `gh pr view` / `gh api` for that PR completed with exit code **0**, **or** you stop in **Get PR Context** with only the failure given there (“No PR found for current branch…”). 2. **Fetch** — **Pass when:** the resolved-thread GraphQL call (skipped if `--include-resolved`) and both paginated `gh api … | jq -s -f …` runs (issue comments + review comments) exit **

What's inside
Steps it walks through
  1. Usage
  2. Instructions
  3. Gates (sequence; do not skip)
  4. 1. Parse Arguments
  5. 2. Get PR Context
  6. 3. Fetch Comments
  7. 4. Format Feedback Document
  8. 5. Evaluate with receive-feedback
  9. Example
Ships with 1 file
  • metadata.json
Commands it runs
If --pr was specified, use that number directly
gh pr view --json number,headRefName,url,author --jq '{number, headRefName, url, author: .author.login}'
Get repo owner/name
gh repo view --json owner,name --jq '{owner: .owner.login, name: .name}'
Get current authenticated user
gh api user --jq '.login'
nodes {
isResolved
cat > /tmp/issue_comments.jq << 'JQEOF'
gh api --paginate "repos/$OWNER/$REPO/issues/$PR_NUMBER/comments" | \
More from claude-skill-registry
All skills →
About this skill
What does the fetch-pr-feedback skill do?

Fetch unresolved review comments from a PR and evaluate with receive-feedback skill

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill fetch-pr-feedback --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going