원클릭으로
review
Run a code review sub-agent
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Run a code review sub-agent
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Post a DRAFT (pending) GitHub PR review made of separate inline review comments anchored to the diff, each with an AI-assisted disclosure and GitHub deep-link permalinks that render as code snippets. Use when the user asks to "add a draft review comment", "post review findings as separate comments", "leave inline review comments", or wants reviewer findings turned into a pending PR review with deep links to the code.
Create a GitHub issue describing the root problem behind current changes, then open a PR that references it
Convert a Marp markdown deck into a fully editable, on-brand PowerPoint (.pptx) built on a Google Slides template's native layouts, carrying speaker notes across, ready to upload to Google Slides. Use when someone wants a Marp deck "in Google Slides", "in the company template", or "as an editable branded deck" rather than rasterized slide images.
Commit, push, and open PR creation in the browser with an empty body for the human to fill in.
Reference for the workmux CLI that manages git worktrees and tmux windows as isolated development environments. Use when the user mentions workmux, worktrees, or parallel agent workflows.
Orchestrate multiple worktree agents. Spawn, monitor, communicate, and merge.
| name | review |
| description | Run a code review sub-agent |
Run a code review of the current changes using the subagent tool with the
reviewer agent: $@
The reviewer agent (~/.pi/agent/agents/reviewer.md) runs in an isolated
context as a separate pi process and streams its tool calls and progress live
into this session, so its work is visible as it happens. The review rubric and
output format live in that agent's prompt; this skill only scopes the diff and
hands it off.
Steps:
Determine the base branch. Use it if given in the arguments above; otherwise
default to the repository's default branch on origin (origin/main, or
origin/master if that is what the repo uses).
Compute the review scope against the base branch's merge-base and enumerate the changed files:
git merge-base HEAD origin/<base>
git diff --stat "$(git merge-base HEAD origin/<base>)"..HEAD
Also detect whether the branch has an associated PR, and if so capture its number/URL so the reviewer can read the intent behind the change:
gh pr view --json number,url,title 2>/dev/null
Call the subagent tool once with agent: "reviewer" and a task that:
git diff "$(git merge-base HEAD origin/<base>)"..HEADgh pr view,
gh issue view) so findings account for stated intent and deliberate
deviations.The subagent tool has no per-call model override; the review model is set
in the reviewer agent's frontmatter. To change it, edit that file.
Do not read the code or run the diff yourself. Let the reviewer subagent do that. When it finishes, report its findings.