pavilio-code-review

Reviews git diffs against project standards and originating specs using parallel sub-agents.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gmotyl/pavilio --skill pavilio-code-review-gmotyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pavilio-code-review
Source: https://github.com/gmotyl/pavilio/tree/main/skills/pavilio-code-review
Command: npx skills add https://github.com/gmotyl/pavilio --skill pavilio-code-review-gmotyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a branch or PR requires checking both code conventions and spec fidelity, and doing both in one pass causes one axis to mask the other. This Skill separates the two concerns into parallel review agents and produces a persistent, structured report. ## Core Features & Use Cases - Two-axis review: A Standards axis checks the diff against documented conventions (PROJECT.md, CONTEXT.md, qa/REVIEW_RULES.md, ADRs), while a Spec axis verifies the code faithfully implements the originating issue, PRD, or plan. - Parallel sub-agents: Both axes run as isolated sub-agents returning emoji-tagged findings tables (🔴 hard, 🟡 judgement, 💡 nit, ✅ pass), then results are aggregated without cross-axis reranking. - Persistent reports: Writes a standalone markdown report to projects/<name>/qa/reviews/ named by date, branch, and short SHA, with idempotent overwrite at the same commit. - Use Case: After finishing a feature branch, run the review against main to get a verdict table, the single worst blocking issue, and a ship / ship-with-follow-up-ticket / fix-first recommendation. ## Quick Start Ask the AI to review the current branch against main using the project's documented standards and the originating spec.

Frequently Asked Questions about pavilio-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a git branch against project coding standards?▼

Run the review with a fixed point such as main or a commit SHA, and the Standards sub-agent compares the diff against PROJECT.md, CONTEXT.md, qa/REVIEW_RULES.md, and ADRs. Findings are returned as a table tagged 🔴, 🟡, 💡, or ✅.

How to check if code implements a spec or PRD correctly?▼

The Spec sub-agent reads the originating issue, PRD, or plan and classifies each finding as missing, scope-creep, wrong, or ok with a spec reference. If no spec exists, that axis is skipped and noted in the report.

What fixed points can I review a diff against?▼

Any valid git ref works: a commit SHA, branch, tag, main, or HEAD~5. The ref is validated with git rev-parse before use, and invalid or shell-unsafe input stops the review with a clarification request.

Where are code review reports saved?▼

Reports are written to <workspace>/projects/<name>/qa/reviews/<date>_CODE_REVIEW_<branch>_<shortSHA>.md. Re-running at the same commit overwrites the same file, while new commits create new files preserving branch history.

Why does the review skip checks that linting tools enforce?▼

Machine-enforced rules from .editorconfig, eslint, biome, prettier, and tsconfig are noted but not re-checked, since tooling already guarantees them. The review focuses on judgment-based standards that automated tools cannot verify.