patch-submission

Prepare and submit PostgreSQL patches to pgsql-hackers and CommitFest.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction and common errors associated with submitting patches to the PostgreSQL community, ensuring your contributions meet the strict standards of the pgsql-hackers mailing list.

Core Features & Use Cases

  • Standardized Workflow: Automates the sequence of rebasing, formatting, and registering patches in the CommitFest system.
  • Quality Assurance: Integrates with self-review gates to ensure patches are ready for committer feedback before submission.
  • Use Case: When you have developed a new feature or bug fix for PostgreSQL, use this skill to prepare your branch, generate the patch series, and register the entry in the CommitFest portal to initiate the review cycle.

Quick Start

Use the patch-submission skill to guide the preparation and submission of the current branch as a new patch series for the PostgreSQL project.

Frequently Asked Questions about patch-submission

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

FAQPage Schema
How do I submit a patch to the PostgreSQL CommitFest?

Submitting a PostgreSQL patch to the CommitFest requires git rebase, format-patch generation, cover letter composition, and registering the entry on the CommitFest portal to initiate the community review cycle.

What is the correct format for a pgsql-hackers mailing list patch submission?

A pgsql-hackers patch submission requires a git format-patch series, a properly composed cover letter, and strict adherence to upstream PostgreSQL coding standards and commit message formatting before sending to the mailing list.

How do I rebase a PostgreSQL feature branch before contributing upstream?

Rebasing a PostgreSQL feature branch for upstream contribution involves aligning your commits with the master branch, verifying commit message formatting, and generating the updated format-patch series for review.

Do I need to follow specific coding standards for PostgreSQL backend patch submission?

Yes, PostgreSQL backend patch submission requires strict adherence to upstream PostgreSQL coding standards, commit message formatting, and passing automated self-review gates before committer feedback.

How does the PostgreSQL patch review cycle bookkeeping work?

Patch review cycle bookkeeping involves tracking your patch status in the CommitFest system, managing rebases for new feedback, and updating the format-patch series to progress through the pgsql-hackers review stages.

What's the best way to manage a PostgreSQL patch series for database internals development?

Managing a PostgreSQL patch series for database internals development requires standardizing the workflow from git rebase to format-patch generation, integrating self-review gates, and tracking the CommitFest registration.