patch-submission
Skill1 starsChanged 6 months agoPostgreSQLView on GitHub
Prepare a PostgreSQL change for upstream submission to pgsql-hackers — covers git format-patch of the series, writing the cover letter, registering a CommitFest (CF) entry, running pgindent / check-world / docs build, and staging the v1 patchset for mailing. Thin wrapper: review machinery lives in pg-patch-review (--self mode) and the commit-message format in commit-message-style. Use whenever a PG patch is being prepared to go upstream — running pgindent before format-patch, writing the cover letter, registering or updating a CF entry, staging v(N+1) re-submission after a review cycle, or running the pre-submission gate (check-world + docs build + pgindent). Skip for GitHub PR creation / `gh pr create` on app repos, NPM publish / crate publish / PyPI / RubyGems release flows, LKML / Linux-kernel patch submission, Apache committer paperwork, generic "how do I contribute to open source" questions, and Gerrit / Phabricator workflows.
- Commits and pushes
In this repository59 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- access-method-apisSkill
- aio-readstreamSkill
- backup-and-recoverySkill
- bgworker-and-extensionsSkill
- buffer-managerSkill
- build-and-runSkill
- catalog-conventionsSkill
- coding-styleSkill
- collation-providerSkill
- commit-message-styleSkill
- copy-familySkill
- corpus-chainSkill
- custom-scan-apiSkill
- debuggingSkill
- error-handlingSkill
- executor-and-plannerSkill
- extended-statisticsSkill
- extension-developmentSkill
- fdw-developmentSkill
- fmgr-and-spiSkill
- free-space-mapSkill
- gucs-configSkill
- jsonpath-and-jsonbSkill
- lockingSkill
- logical-replicationSkill
- memory-contextsSkill
- memory-keepingSkill
- meta-commit-styleSkill
- multixactSkill
- node-infrastructureSkill
- parallel-querySkill
- parser-and-nodesSkill
- pg-claudeSkill
- pg-feature-brainstormSkill
- pg-feature-planSkill
- pg-implementSkill
- pg-patch-reviewSkill
- pg-shadow-implementSkill
- pgstat-frameworkSkill
- pg-upgrade-internalsSkill
- physical-replicationSkill
- planner-cost-modelSkill
- plpgsql-internalsSkill
- process-lifecycleSkill
- psqlSkill
- replication-overviewSkill
- resource-ownersSkill
- review-checklistSkill
- row-level-securitySkill
- slru-infrastructureSkill
- snapshot-managementSkill
- testingSkill
- toast-storageSkill
- type-cacheSkill
- vacuum-autovacuumSkill
- wal-and-xlogSkill
- wire-protocolSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.