Skip to content
Back to skills

Address Pr Review

ASecurity

Handle PR feedback, address review comments, fix PR issues, respond to reviewer. Use when PR has comments to address, need to resolve feedback, or reviewer requested changes.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentsbashnodeapi

Works with

  • api

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill address-pr-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Address Pr Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Address Pr Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-address-pr-review/badge)](https://www.skillsdirectory.com/skills/david-li0406-address-pr-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: address-pr-review
description: Handle PR feedback, address review comments, fix PR issues, respond to reviewer. Use when PR has comments to address, need to resolve feedback, or reviewer requested changes.
argument-hint: PR number or URL
disable-model-invocation: true
context: fork
---

# Address PR Review

Address unresolved PR review comments for pull request $ARGUMENTS.

## Process

### 1. Fetch Unresolved Comments

Parse PR number from `$ARGUMENTS` (numeric or extract from URL).

Get PR details:

```bash
gh pr view [PR_NUMBER] --json number,title,url,headRepositoryOwner,headRepository
```

Fetch unresolved threads via GraphQL:

```bash
gh api graphql -f query='
query {
  repository(owner: "OWNER", name: "REPO") {
    pullRequest(number: PR_NUMBER) {
      reviewThreads(first: 50) {
        nodes {
          isResolved
          comments(first: 10) {
            nodes {
              id
              body
              path
              line
              author {
                login
              }
              createdAt
            }
          }
        }
      }
    }
  }
}' --jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false) | {isResolved: .isResolved, comment: .comments.nodes[0]}'
```

### 2. Launch PR Comment Reviewer Agents

Launch one `pr-comment-reviewer` agent per unresolved comment. Use Task tool with `subagent_type: "pr-comment-reviewer"`.

**Launch all agents in parallel** using multiple Task calls in a single message.

Prompt structure:

```
Review this PR comment and evaluate whether the suggested change should be implemented:

**File**: {path}
**Line**: {line}
**Author**: {author}
**Comment**:
{body}

Provide a critical but reasonable evaluation of:
1. Whether this change is necessary
2. The proposed solution (if any) vs alternatives
3. Your recommendation
```

### 3. Generate Report

Consolidate agent responses into a summary:

```markdown
# PR Review Comment Analysis for PR #{number}

Found {N} unresolved comments.

## Summary

- **Should Fix**: {count} comments
- **Optional**: {count} comments
- **Skip**: {count} comments

---

## Comment 1: {Short description}

**File**: {path}:{line}
**Verdict**: {Should Fix / Optional / Skip}

{Agent's reasoning and recommendation}

---

## Overall Recommendation

{Synthesized recommendation across all comments}
```

## Guidelines

- Only analyze unresolved comments (`isResolved == false`)
- Launch agents in parallel for speed
- Be critical but reasonable about recommendations
- Consider CLAUDE.md principles when evaluating suggestions
- Consolidate duplicate comments
- Use clear verdicts: Should Fix, Optional, or Skip

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…