Menu
Fetch PR review comments and propose specific fixes
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | resolve-reviews |
| description | Fetch PR review comments and propose specific fixes |
| argument-hint | <PR number or URL> |
| allowed-tools | ["Read","Grep","Glob","Bash"] |
| context | fork |
You are resolving PR review comments. Fetch all review feedback, analyze the code, and propose specific fixes.
You do NOT modify files. You analyze and propose only. The user decides what to apply.
gh pr view --json number --jq '.number'
Run these in parallel:
# PR overview (title, base branch, changed files)
gh pr view <number> --json title,baseRefName,files,headRefName
# PR diff (to understand full changeset)
gh pr diff <number>
Fetch all 3 types of comments:
# 1. Inline review comments (file/line specific)
gh api repos/{owner}/{repo}/pulls/<number>/comments \
--jq '.[] | {id, user: .user.login, path: .path, line: .line, body: .body}'
# 2. General PR comments (conversation)
gh api repos/{owner}/{repo}/issues/<number>/comments \
--jq '.[] | {id, user: .user.login, body: .body}'
# 3. Review-level comments (top-level review body)
gh pr view <number> --json reviews \
--jq '.reviews[] | select(.body | length > 0) | {user: .author.login, state: .state, body: .body}'
For each comment:
[bot] or github-actions)path and line -> read the specific fileFor each actionable comment:
Present the report in this format:
## PR #<number> Review Resolution
**PR**: <title>
**Branch**: <head> → <base>
**Resolved**: N items (inline: X, general: Y)
---
### 1. [path/to/file.ts:42] Comment summary
**Reviewer**: @username
**Comment**:
> Original quote
**Proposal**:
\`\`\`diff
- before
+ after
\`\`\`
**Rationale**: Why this fix is appropriate
---
### 2. [General] Comment summary
**Reviewer**: @username
**Comment**:
> Original quote
**Proposal**: Specific resolution description
---
If there are no actionable comments, report:
No actionable review comments found.
Perform a comprehensive code quality review
TypeScript and Next.js coding standards. Auto-triggered when writing, reviewing, or refactoring TypeScript/React code. Covers type patterns, component patterns, Biome rules, and import conventions.
React and Next.js frontend design patterns. Auto-triggered when creating React components, implementing data fetching, managing state, or optimizing performance. Covers Server Components, Suspense, streaming, and rendering.
Create a structured implementation plan for a feature or task
Access NotebookLM to ask questions and retrieve information. Specify a NotebookLM URL and query.
Safely refactor code while preserving test behavior