pg-patch-review

Orchestrate multi-agent review pipelines for PostgreSQL patches with automated build and test cycles.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/matejformanek/postgres-claude --skill pg-patch-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pg-patch-review
Source: https://github.com/matejformanek/postgres-claude/tree/main/.claude/skills/pg-patch-review
Command: npx skills add https://github.com/matejformanek/postgres-claude --skill pg-patch-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the bottleneck of manual, error-prone PostgreSQL patch reviews by orchestrating a multi-agent pipeline that performs mechanical validation and deep architectural analysis.

Core Features & Use Cases

  • Parallel Critic Fan-out: Simultaneously runs five specialized agents to evaluate architecture, breaking changes, test coverage, style, and persona-driven reviewer reflexes.
  • Automated Synthesis: Generates a professional, mailing-list-ready review email in the official PostgreSQL hackers style.
  • Use Case: Use this when you need to provide a comprehensive, cited review for a CommitFest entry or GitHub PR, ensuring the patch adheres to complex internal invariants and coding standards.

Quick Start

Invoke the pg-patch-review skill by providing the patch reference such as a CF number or PR link to initiate the full multi-agent analysis pipeline.

Frequently Asked Questions about pg-patch-review

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

FAQPage Schema
How do I automate PostgreSQL patch review for CommitFest entries or GitHub pull requests?

You can automate PostgreSQL patch review by providing a CommitFest entry number or GitHub PR link to trigger a multi-agent pipeline. This pipeline executes mechanical build and regression test cycles, followed by parallel architectural and stylistic analysis against the PostgreSQL source tree.

What is the best way to generate mailing-list-ready review feedback for PostgreSQL patches?

Generating mailing-list-ready review feedback involves synthesizing automated regression testing and invariant checking results into a professional email. A multi-agent pipeline evaluates architecture, breaking changes, test coverage, and style to produce cited feedback in the official PostgreSQL hackers format.

Can I run multi-agent code review on local PostgreSQL patch files?

Yes, you can run multi-agent code review on local patch files. The pipeline performs deep-dive verification against the PostgreSQL source tree, applying automated regression testing and invariant checking to ensure patches adhere to internal coding standards.

Does automated PostgreSQL patch review check for breaking changes and test coverage?

Automated PostgreSQL patch review checks for breaking changes and test coverage by fanning out parallel specialized agents. These agents simultaneously evaluate architecture, breaking changes, test coverage, coding style, and persona-driven reviewer reflexes for comprehensive verification.

What are the limitations of multi-agent database patch review for PostgreSQL?

Multi-agent database patch review for PostgreSQL requires deep-dive verification against the PostgreSQL source tree, meaning local build environments must support mechanical test cycles. The pipeline focuses on PostgreSQL-specific invariants and may not generalize to other database systems.