원클릭으로 Manus에서 모든 스킬 실행

시작하기

resolve-reviews

스타0

포크0

업데이트2026년 2월 13일 05:02

Fetch PR review comments and propose specific fixes

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

thirdlf03

thirdlf03/ccpeek

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Instructions

Step 1: Identify PR

If the user provided a PR number or URL, use that

Otherwise, auto-detect from current branch:

gh pr view --json number --jq '.number'

If no PR is found, inform the user and stop

Step 2: Fetch PR Info

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>

Step 3: Fetch Review Comments

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}'

Step 4: Filter & Classify

For each comment:

Skip bot comments (user contains [bot] or github-actions)
Skip approval-only reviews with no actionable feedback ("LGTM", "Approved" etc.)
Classify as:
- Inline: Has path and line -> read the specific file
- General: No file reference -> refer to PR diff for context

Step 5: Analyze & Propose

For each actionable comment:

Read the relevant source file (for inline comments, focus on the referenced lines)
Understand what the reviewer is requesting
Propose a specific fix with a diff block

Step 6: Output Report

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.

Rules

NEVER modify files. You are read-only. Propose only.
Always quote the original comment so the user can verify context
Include file:line references for every inline comment
If a comment is ambiguous, note the ambiguity and propose the most likely interpretation
Group related comments on the same file together when possible

이 저장소의 다른 Skills

같은 저장소

code-review

thirdlf03/ccpeek

Perform a comprehensive code quality review

2026-02-130

coding-standards

thirdlf03/ccpeek

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.

2026-02-130

frontend-patterns

thirdlf03/ccpeek

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.

2026-02-130

my-plan

thirdlf03/ccpeek

Create a structured implementation plan for a feature or task

2026-02-130

notebooklm-query

thirdlf03/ccpeek

Access NotebookLM to ask questions and retrieve information. Specify a NotebookLM URL and query.

2026-02-130

refactor

thirdlf03/ccpeek

Safely refactor code while preserving test behavior

2026-02-130

# 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}'

## 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 ---

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