pr-review

PR Review — 3-Phase Orchestrator

End-to-end PR review workflow that orchestrates phases to explore independent fix alternatives and produce a recommendation.

Trigger phrases: "review PR #XXXXX", "work on PR #XXXXX", "fix issue #XXXXX"

🚨 NEVER use gh pr review --approve or --request-changes. AI agents must NEVER post review comments. 🚨 DO NOT post any comments to the PR. This skill only produces output files in CustomAgentLogsTmp/PRState/.

---

Overview

Gate (pre-run)    → Already completed by Review-PR.ps1 before this skill runs
Phase 1: Pre-Flight   → Gather context, classify files, code review     → .github/pr-review/pr-preflight.md
Phase 2: Try-Fix      → ⚠️ MANDATORY multi-model exploration           → invoke try-fix skill (×4 models)
Phase 3: Report       → Write review recommendation                     → .github/pr-review/pr-report.md

Gate and Branch setup are handled by Review-PR.ps1 before this skill is invoked. The gate result is passed in the prompt. Do NOT re-run gate verification.

All phases write output to: CustomAgentLogsTmp/PRState/{PRNumber}/PRAgent/{phase}/content.md Pre-Flight also writes: CustomAgentLogsTmp/PRState/{PRNumber}/PRAgent/pre-flight/code-review.md

---

Critical Rules

• ❌ Never run git checkout or git switch to change branches — stay on the review branch set up by the caller
• ❌ Never stop and ask the user — use best judgment to skip blocked phases and continue
• ❌ Never mark a phase complete with pending fields
• ❌ Never skip Phase 2 multi-model exploration — it is MANDATORY for every review, no exceptions
• ❌ Never run git commands that change branch state during Phases 2-3 (scripts handle file manipulation)
• ❌ Never duplicate phase content — each phase writes ONLY to its own content.md. Do NOT copy gate results into try-fix or report content files.
• ✅ Always create CustomAgentLogsTmp/ output files for every phase
• ✅ Always include Co-authored-by: Copilot <[email protected]> in any commits
• ✅ Always use skills' scripts — don't bypass with manual commands
• ✅ Each phase's content.md must use the exact template from the phase instruction doc — no extra prose