PR Review Agent

Purpose

Run a focused PR review that checks only implemented changes against ticket context and flags real risks/regressions.

Runtime Configuration

Read
```
/orchestra-config.json
```
from the repository root before starting.
Read
```
issue_tracker
```
and use only the configured tracker MCP for ticket operations.
Use the MCP mapped to
```
issue_tracker
```
in
```
orchestra-config.json
```
.
If the configured issue tracker MCP is unavailable, stop immediately and do not proceed with the task.
For every tracker comment/status update, include:
```
Skill-Version: pr-review-agent@1.3.0
```
.

When to Invoke

When a PR is ready for review and linked to an issue.

Required Inputs

Parent issue ID
Parent issue tag
```
pr-published
```
Linked PR and PR diff / changed files
Issue summary
Acceptance criteria
```
technical-details
```
subtask content

Outputs

PR comment:
Short review summary
Findings that require changes (if any), tied to the changed code
Issue tracker comment:
Short review summary
Required changes checklist (if any)
Status update:
```
In Progress
```
when changes are required
```
Done
```
when changes are acceptable
Parent issue tags:
```
pr-reviewed
```
when review is clean
```
open-pr-review-questions
```
when review is blocked by missing context
Structured parent handoff comment:

text

Workflow-Handoff:
From: pr-review-agent
To: implementation-agent|none
Status: ready|blocked|completed
Open-Questions: none|<question list>
Skill-Version: pr-review-agent@1.3.0

Procedure

Read
```
/orchestra-config.json
```
from the repository root, set tracker context, and verify the configured issue tracker MCP is available.
Validate parent issue has tag
```
pr-published
```
.
Check only prior-stage open-question signal:

If tag

open-pr-publish-questions

exists, read only the latest

Workflow-Handoff

from

pr-publish-agent

, then stop.

Fetch from the issue:
- issue summary
- acceptance criteria
- ```
technical-details
```
  subtask
Fetch only the PR changes (diff/changed files). Do not review unchanged files.
Review scope is limited to:
- correctness and regression risk in changed code
- alignment with
```
technical-details
```
- acceptance criteria coverage
- pattern consistency with the technical details
Do not over-engineer:
- avoid unnecessary optimizations or style-only nits
- report only issues that can cause bugs, regressions, broken behavior, or criteria mismatch
Post a short PR comment with:
- overall result (
```
changes required
```
  or
```
looks good
```
  )
- concise findings list (or explicit
```
no blocking issues found
```
  )
Post a short issue tracker comment with the same outcome summary and key findings.
If review is blocked by missing context (for example unclear acceptance criteria or missing technical details):

Add
```
open-pr-review-questions
```
.
Add
```
Workflow-Handoff
```
with
```
Status: blocked
```
.
Stop and wait for clarifications.

If required code changes are found and review is not blocked:

Remove
```
open-pr-review-questions
```
if present.
Set issue status to
```
In Progress
```
.

Add

Workflow-Handoff

with

To: implementation-agent

and

Status: ready

Invoke
```
implementation-agent
```
with the same parent issue ID.

If no required changes remain:

Remove
```
open-pr-review-questions
```
if present.
Add tag
```
pr-reviewed
```
.
Set issue status to
```
Done
```
.

Add

Workflow-Handoff

with

To: none

and

Status: completed

Do not invoke further skills.

Guardrails

Use only: PR changes, issue summary, acceptance criteria, and
```
technical-details
```
.
Do not read the full repository for this review.
Prioritize correctness and functional risk over stylistic preferences.
Keep findings actionable and tied to specific changed files.
Do not run tracker operations unless the MCP for the configured
```
issue_tracker
```
is available.
Keep PR and tracker comments concise; do not paste raw command logs (including
```
pnpm list
```
/
```
pnpm build
```
output dumps).
For open-question checks, do not read full comment history; read only the previous agent's latest
```
Workflow-Handoff
```
comment.

Handoff

Primary consumer:

implementation-agent

for fixes, then this agent reruns until clean.

pr-review-agent

NPX Install

Tags

SKILL.md Content