Address PR Review

Look at the pull request review comments and address any issues raised.

15 stars 3 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mnapoli/skill-address-pr-review --skill address-pr-review
Manual install
git clone --depth 1 https://github.com/mnapoli/skill-address-pr-review.git /tmp/skill-address-pr-review
mkdir -p ~/.claude/skills
cp -r /tmp/skill-address-pr-review/. ~/.claude/skills/address-pr-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

## Step 1: Fetch unresolved review threads and CI status

Run both helper scripts:

```bash
bash ./get-unresolved-threads.sh
```

```bash
bash ./get-failing-ci.sh
```

The first returns a JSON array of unresolved threads. Each thread has:
- `id` — thread ID (needed to reply)
- `path` — file path
- `line` / `startLine` — line numbers in the diff
- `isOutdated` — whether the diff has changed since the comment
- `comments.nodes[]` — the comment thread (first = original comment, rest = replies), each with `author.login`, `body`, and `url`

The second checks CI status and outputs failure details if any jobs failed (exit code 1 = failures, 0 = all passed).

If there are no unresolved threads and CI is green, stop here.

## Step 2: Address each issue

If there are many items, create one task per item to keep things organized.

For each unresolved review thread:

1. Read the comment thread to understand the issue
2. Determine if a code change is needed, or if no change is needed (e.g. the comment is invalid or the suggestion is not appropriate)
3. If a change is needed, make the necessary code changes

For each CI failure:

1. Read the failure output to understand what broke
2. Fix the code or tests to make CI pass

## Step 3: Commit and push changes

After addressing all review comments and CI failures, commit your changes and push.

## Step 4: Reply to each review thread

After addressing each comment, reply using the helper script:
Read the full skill on GitHub

Details

Skill name
address-pr-review
License
MIT
Repo updated
8 July 2026

FAQ

What does the Address PR Review skill do?

Look at the pull request review comments and address any issues raised.

How do I install the Address PR Review skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add mnapoli/skill-address-pr-review --skill address-pr-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Address PR Review popular?

It lives in mnapoli/skill-address-pr-review, which has 15 GitHub stars and 3 forks.

Related skills

Build It

16

DevOtts/build-it

Autonomous goal-to-DoD delivery orchestrator — the build stage of the *-it lifecycle ("plan-it plans it, build-it builds it"); formerly named fable-it. Hand it a goal and a numbered Definition of Done and it runs the whole job to completion, typically unattended, enforcing checkable gates (turn-end, claim, state-change, phase-boundary, delegation, and safe-parallel: interlock, worktree, integration), disk-backed run state, an evidence ledger that makes VERIFIED a lookup, a fresh-eyes verification pass, and an honest per-criterion report. Model-adaptive for Sonnet 5 and Opus 4.8; host-agnostic

Git & Code Review

Github Demand Radar

16

geekjourneyx/github-demand-radar

Use when the user asks to analyze a GitHub repository's issues/PRs to identify high-value commercial demand opportunities. Triggers: 「扫issue」「扫PR」「找需求」「分析仓库」「找商业化点子」「独立开发者切入点」「需求雷达」「扫一下明星项目」「生成需求报告」. Outputs scored demand cards with JTBD analysis, RICE scoring, Ugly Workaround evidence, and fake-door probe drafts. Also works in PR scan mode (Phase 1B) to find rejected/stale PRs as market gap signals.

Git & Code Review

Recat Web

12

0xtbug/Recat

Automatically install and set up the Recat website from github.com/0xtbug/Recat, including prerequisites, dependencies, local password, findings folder, build, and server startup. Also use to repair or develop an existing Recat installation.

Git & Code Review

Repo to Skill

19

shuyhere/repo-to-skill

Generate an agent skill from a GitHub open-source repository. Use when asked to create a skill from a repo URL, turn a GitHub project into a usable skill, or generate skill files for a CLI/library/framework. Triggers on phrases like "create a skill from this repo", "make a skill for vllm", "turn this GitHub project into a skill", "generate a skill from repo". Also use when asked to "skillify" a tool or generate usage instructions from source code. Command usage — `/skill repo-to-skill <github-repo-url>`.

Git & Code Review

Gh Actions

11

retlehs/gh-actions

GitHub Actions best practices — current action versions, caching, security, and common patterns. Activate when writing or modifying GitHub Actions workflows.

Git & Code Review

Github Stars Curator

22

Leexunhuan743/github-stars-curator

Organize starred GitHub repos into stable, clear lists: detect new stars, download READMEs into a local corpus, classify each repo against the taxonomy, and sync the approved mapping back to GitHub via gh. Use this when a user wants their starred repos sorted into lists, a recent batch of new stars filed incrementally, or their star-list taxonomy reviewed and refined. Do not use for general GitHub issue/PR management, repo code search, or bookmarking non-GitHub resources.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.