Add PostgreSQL AI Hacking Tools documentation #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NikolayS
force-pushed
the
claude/review-postgres-discussions-n0hWB
branch
2 times, most recently
from
2362f0f to
fe60593
Compare
Create REV/CLAUDE.md with comprehensive subagents and workflows for AI-assisted PostgreSQL patch development. This includes: - 15 specialized subagents covering the full patch lifecycle: - Building and testing (pg-build, pg-test, pg-benchmark) - Code quality (pg-style, pg-review, pg-coverage) - Patch management (pg-patch-create, pg-patch-version, pg-patch-apply) - Communication (pg-hackers-letter, pg-commitfest, pg-feedback) - Documentation and debugging (pg-docs, pg-debug) - Final validation (pg-readiness) - Complete workflows for new features, bug fixes, and patch review - Critical human checkpoints that cannot be automated - Common pitfalls and how to avoid them - References to official PostgreSQL development resources Based on research of recent pgsql-hackers discussions and the CommitFest process at commitfest.postgresql.org.
Restructure REV/ to use proper Claude Code subagent format: - Create .claude/agents/ directory with 15 specialized agents - Each agent has proper YAML frontmatter (name, description, model, tools) - Each agent has veteran Postgres hacker role definition - Critical agents (pg-review, pg-readiness, pg-hackers-letter, pg-feedback) use opus model for higher quality output Agents by category: Development & Build: - pg-build: Build PostgreSQL with various configurations - pg-test: Regression and TAP testing - pg-benchmark: Performance testing with pgbench - pg-debug: GDB debugging and core dump analysis Code Quality: - pg-style: pgindent and coding conventions - pg-review: AI-assisted code review (opus) - pg-coverage: Test coverage analysis - pg-docs: DocBook SGML documentation Patch Management: - pg-patch-create: Create clean patches - pg-patch-version: Manage versions and rebasing - pg-patch-apply: Apply and test others' patches Community Interaction: - pg-hackers-letter: Write pgsql-hackers emails (opus) - pg-commitfest: Navigate CommitFest workflow - pg-feedback: Address reviewer feedback (opus) Quality Gate: - pg-readiness: Comprehensive submission checklist (opus) Updated CLAUDE.md to serve as index referencing the agents.
Prefer 'Postgres' over 'PostgreSQL' throughout all agent files and CLAUDE.md for consistency.
In the AI era, drafting code is fast. A working prototype speaks louder than abstract discussion. Updated lifecycle and pitfalls to reflect this new approach.
AI can assist with architectural fit evaluation and help craft reasoning for building consensus through better email communication.
Subagents are invoked via natural language like: 'Use the pg-review subagent to check my patch' Not via @ prefix syntax.
- /pg-ready: Check patch readiness for submission - /pg-submit: Prepare patch and draft email - /pg-respond: Help respond to reviewer feedback Slash commands provide quick access to common actions.
NikolayS
force-pushed
the
claude/review-postgres-discussions-n0hWB
branch
from
fe60593 to
e0fe9e6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create REV/CLAUDE.md with comprehensive subagents and workflows for AI-assisted PostgreSQL patch development. This includes:
15 specialized subagents covering the full patch lifecycle:
Complete workflows for new features, bug fixes, and patch review
Critical human checkpoints that cannot be automated
Common pitfalls and how to avoid them
References to official PostgreSQL development resources
Based on research of recent pgsql-hackers discussions and the CommitFest process at commitfest.postgresql.org.