Look at the pull request review comments and address any issues raised.
Scanned 5/27/2026
Install via CLI
Skills Directoryopenskills install mnapoli/skill-address-pr-review---
description: Look at the pull request review comments and address any issues raised.
disable-model-invocation: true
context: fork
allowed-tools: Bash(bash ~/.claude/skills/address-pr-review/*)
---
## 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:
```bash
bash ./reply-to-thread.sh "<thread_id>" "<body>" [--resolve]
```
- If the code was fixed as mentioned in the thread, reply with simply: "Fixed as suggested." and pass `--resolve` to mark the thread as resolved.
- If no change was applied, briefly explain why and keep the thread unresolved (omit `--resolve`) so the reviewer can reply if they disagree.
- Don't be unnecessarily verbose.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...
