メニュー
Comprehensive PR review using specialized agents. Use when asked to review a pull request, check code quality before merging, or run any subset of review aspects (code, tests, errors, types, docs, simplify).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when starting feature work that needs isolation from current workspace, before executing implementation plans, or when reviewing an existing branch (e.g. a PR) without switching away from the current branch. It creates isolated git worktrees under `.worktrees/`.
Use this skill when working on terminal UI rendering, interactive CLI prompts, ANSI color output, terminal screenshots, Bubble Tea/Lip Gloss/Huh/Glamour, curses-style apps, or CLI tests that depend on TTY behavior.
Use this skill when you're working with golang code.
Use whenever asked to create GitHub Pull Request.
Use when writing, rewriting, or updating a pull request description. Use this skill's explicit PR template unless the user provides a different template for the current task, keep the result concise and human-readable, explain why the change exists, and ask the user for motivation before updating the PR when the user has not explicitly provided it.
Use this skill whenever writing, editing, reviewing, or deciding whether to add code comments, docstrings, inline comments, or internal function documentation in any programming language. Use it even when the task only mentions "comments", "docs in code", "docstrings", "document this function", or "explain this helper".
| name | review-pr |
| description | Comprehensive PR review using specialized agents. Use when asked to review a pull request, check code quality before merging, or run any subset of review aspects (code, tests, errors, types, docs, simplify). |
| allowed-tools | Bash(*scripts/gather-requirements.sh*) Bash(*scripts/review-meta.sh*) Bash(jira issue view*) Bash(mkdir -p */agents/pr-review/*) Edit(**/agents/pr-review/*/*.json) Write(**/agents/pr-review/*/*.json) |
Checkout the PR Branch
Use the git-worktrees skill to create an isolated checkout of the PR branch:
Pass the branch name to check out. The worktree will be created at
.worktrees/<branch-name>. All subsequent steps operate from within
that worktree path.
Determine Review Scope
From within the worktree, run git diff --name-only origin/HEAD...HEAD to identify changed files
Check if specific aspects were requested; default to all
Prepare the output file and capture metadata:
$DOTFILES/config/agents/skills/review-pr/scripts/review-meta.sh
Read the JSON output directly from the tool result:
outfile, repo, branch, commit_id, pr_number.
Gather Requirements Context
Run the requirements-gathering script:
$DOTFILES/config/agents/skills/review-pr/scripts/gather-requirements.sh
Read the JSON output: source, issue_ref, requirements.
If source is "none", use AskUserQuestion:
I couldn't find linked requirements for this PR. Please paste the requirements, acceptance criteria, or issue description — or type
skipto omit the spec review.
If jira_attempted is true and source is "none",
mention the Jira key that was tried
and ask the user to paste the ticket description.
Store the collected requirements text as REQUIREMENTS.
If the user types skip, omit the spec review from the run.
Determine Applicable Reviews
Based on changes:
_test.go or test files changed: test-analyzerSkip requirements-verifier only if REQUIREMENTS is empty (user typed skip).
Launch Review Agents
Default: sequential (one at a time, easier to act on). If user requests parallel, launch all simultaneously.
Requirements-verifier — use spec-reviewer subagent type.
Pass the following context in the prompt:
REQUIREMENTS text collected in step 3git diff --name-only origin/HEAD...HEADgit diff origin/HEAD...HEADAggregate Results
# PR Review Summary
## Critical Issues (X found)
- [agent]: description [file:line]
## Important Issues (X found)
- [agent]: description [file:line]
## Suggestions (X found)
- [agent]: suggestion [file:line]
## Recommended Action
1. Fix critical issues first
2. Address important issues
3. Consider suggestions
4. Re-run review after fixes
Persist Results
Write findings to the outfile path from step 2 using this schema:
{
"version": 1,
"timestamp": "<ISO 8601 UTC>",
"repo": "<owner/repo from gh repo view>",
"branch": "<current branch>",
"commit_id": "<HEAD sha>",
"pr_number": <number or null>,
"aspects": ["<aspects that were run>"],
"findings": [
{
"severity": "critical | important | suggestion",
"agent": "<agent name>",
"file": "<relative file path or null>",
"line": <line number or null>,
"description": "<finding text>"
}
],
}
Report the output path to the user.
Offer to Post Review to GitHub
Use AskUserQuestion to ask:
Would you like to post these findings as a GitHub PR review?
If yes, invoke the github-post-pr-review skill.
/agents list$XDG_DATA_HOME/agents/pr-review/