Pi Review

What it does

Pi Review turns code review into a repeatable workflow inside Pi. Running /review opens a selector (or accepts direct arguments) to review uncommitted changes, a base branch, a specific commit, a GitHub pull request, or a folder snapshot, and automatically loads project-specific rules from REVIEW_GUIDELINES.md.

By default it branches or clones the session so review findings do not clutter implementation history. When the review finishes, /end-review can jump back to your original session position, carry back a structured summary, or return and immediately queue fixes for the agent-actionable findings.

When to reach for it

Invocation: Run /review before committing or opening a PR, then finish with /end-review.

Pre-commit self-review

Review uncommitted working-copy changes against REVIEW_GUIDELINES.md and fix high-priority issues in one loop.

Branch or PR review

Inspect a feature branch or GitHub pull request without losing your place in the current coding session.

What it adds

• /review command supporting uncommitted diffs, branches, commits, GitHub PRs (via gh), folders, and custom instructions.
• /end-review wizard with three exit paths: return only, return and summarize, or return and fix.
• Structured severity levels (critical, high, medium, low) split between agent-actionable findings and human callouts.

Commands: /review, /review branch <name>, /review commit <sha>, /review pr <number-or-url>, /review folder <paths>, /end-review

How it fits

• Test Audit — Pair during pre-commit checks: Pi Review audits production diffs while Test Audit checks whether new tests earn their keep.
• Pi Progress Bar — Run Pi Review once Pi Progress Bar shows all implementation and test requirements have settled as done.

Good to know

• Pull request reviews require the GitHub CLI (gh) and switch the working tree to the PR checkout.

Source and setup

Source

https://github.com/earendil-works/pi-review

Loaded via

git:github.com/earendil-works/pi-review

Attribution

By Earendil