← ClaudeAtlas

pg-patch-reviewlisted

Run a multi-agent comprehensive review of a PostgreSQL patch (CommitFest entry, GitHub PR, or local .patch file) — orchestrates the mechanical pre-amble (fetch + apply + build + regress / iso / TAP) and then fans out 5 critic sub-agents IN PARALLEL (architecture / invariants critic cross-checking knowledge/subsystems/*.md INV-* tags, breaking-change critic for on-disk / WAL / catalog / extension-ABI, test-coverage critic, style / commit-message critic, reviewer-reflex critic against knowledge/calibration/gap-catalog.md), then synthesizes one PG-house-style review email. Stage 3 verdict supports REJECT-A/B/C grades for design-level rejections. Use when the user says "/pg-review <CF# | PR# | patchfile>", "deep-review this patch", "comprehensive review of CF NNNN", "mailing-grade review of this patch", or "run the 5-critic fan-out on <patch>". Skip for non-PG patch review, self-review-before-mail (use patch-submission), the lightweight 7-phase walk (use review-checklist), generic GitHub PR review (use review-cha
matejformanek/postgres-claude · ★ 0 · Code & Development · score 70
Install: claude install-skill matejformanek/postgres-claude
# pg-patch-review — multi-agent comprehensive PG patch review The deep-review counterpart to the manual seven-phase `review-checklist`. The cf6402 validation run on 2026-06-02 proved the corpus + skills compose for a one-author review; this skill turns that loop into a repeatable multi-agent pipeline. ## When to use this skill vs `review-checklist` | Situation | Use | |---|---| | CF entry you intend to mail a real review on | **this skill** | | Quick "is this even sane?" pass on a patch | `review-checklist` (manual seven-phase) | | Self-review of your own patch before mailing | `patch-submission` (which already invokes `review-checklist`) | | Generic non-PG GitHub PR review | neither — this is PG-specific | The two are NOT redundant: `review-checklist` is the seven-phase scaffold each critic agent applies inside its assigned slice. This skill is the **orchestration layer** above that scaffold (project discovery + parallel critic fan-out + synthesis). ## Companion skills (each critic loads what it needs) - `review-checklist` — seven-phase scaffold each critic walks inside its slice - `wal-and-xlog` — WAL records / redo / hint bits (used by breaking-change critic) - `locking` — lock primitive choice + acquisition order (architecture critic) - `catalog-conventions` — `pg_proc` / OID assignment (breaking-change critic) - `testing` — regress vs isolation vs TAP vs module (test-coverage critic) - `coding-style` — pgindent / include order / C99 subset (style critic) - `commit-