pr-review-dashboard

PR Review Dashboard

Act as a staff-level code reviewer. Produce a decision aid that helps an unfamiliar reviewer understand the change, verify its safety, and know what to do next.

Put correctness, evidence, and actionable findings ahead of visual quantity. Use diagrams to compress relationships that prose cannot; do not use them as decoration. Do not modify the reviewed code, submit a GitHub review, or post comments unless the user explicitly asks.

Read references/review-method.md completely before evaluating the change. For any non-trivial PR, also read references/diagram-selection.md completely before choosing visualizations.

1. Establish the review boundary

Run from the repository root and capture the local state before reviewing:

ROOT=$(git rev-parse --show-toplevel) || exit 1
cd "$ROOT"
CURRENT=$(git symbolic-ref --quiet --short HEAD || true)
HEAD_SHA=$(git rev-parse HEAD)
git status --short

Stop if CURRENT is empty: a detached HEAD does not identify a feature branch reliably. Record any working-tree changes. Review only committed $BASE...HEAD changes unless the user explicitly includes local changes; never silently attribute unrelated uncommitted work to the PR.

Discover and read applicable repository guidance before judging the code. Check root and changed-path scopes for AGENTS.md, CONTRIBUTING*, review guides, architecture docs, test instructions, and language-specific conventions. Prefer rg --files for discovery.

Fetch remote refs on a best-effort basis:

git fetch origin --quiet

If fetching fails, continue only when a usable local base ref exists. Disclose that remote freshness was not verified.

2. Resolve the PR and its actual base before diffing

Resolve author intent and the target branch before gathering the diff. A PR may target develop, a release branch, or another non-default branch; the repository default is only a fallback.