Add slash commands for common workflows

- /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.

Author: claude

REV/.claude/commands/pg-ready.md

@@ -0,0 +1,12 @@
+Evaluate patch readiness for pgsql-hackers submission.
+
+You are a veteran Postgres hacker. Check:
+
+1. **Build**: Does it compile clean? Run `make -j$(nproc) 2>&1 | grep -E 'warning:|error:'`
+2. **Tests**: Do all tests pass? Check `make check` status
+3. **Style**: Is pgindent run? Check modified .c/.h files
+4. **Debug code**: Any printf/elog DEBUG/#if 0 left? `git diff HEAD~1 | grep -E 'printf|elog.*DEBUG|#if 0'`
+5. **Docs**: For user-visible changes, is documentation updated?
+6. **Commit message**: Is it clear and properly formatted?
+
+Give a clear **READY** or **NOT READY** verdict with specific issues to fix.

REV/.claude/commands/pg-respond.md

@@ -0,0 +1,16 @@
+Help respond to pgsql-hackers review feedback.
+
+You are a veteran Postgres hacker. Given the feedback:
+
+1. **Parse feedback**: List each point raised by reviewers
+2. **Categorize**:
+   - Must fix (bugs, missing tests)
+   - Should fix (style, suggestions from senior hackers)
+   - Discuss (alternative approaches, disagreements)
+3. **Draft response**: For each point:
+   - If accepting: "Good catch! Fixed in v2..."
+   - If disagreeing: "I considered X, but chose Y because..."
+   - If clarifying: "Could you elaborate on..."
+4. **Changelog**: Summarize changes for the email
+
+Output a complete reply email ready to send.

REV/.claude/commands/pg-submit.md

@@ -0,0 +1,16 @@
+Prepare patch for pgsql-hackers submission.
+
+You are a veteran Postgres hacker. Help prepare and submit:
+
+1. **Generate patch**: `git format-patch master --base=master`
+2. **Verify applies**: Test that patch applies cleanly
+3. **Draft email**: Write cover letter with:
+   - Clear subject: `[PATCH] Brief description`
+   - Motivation: Why is this needed?
+   - Implementation: Brief approach description
+   - Testing: What was tested?
+   - Any open questions
+
+Output the complete email ready to send to pgsql-hackers@lists.postgresql.org
+
+Remind about registering in CommitFest after submission.

REV/CLAUDE.md

@@ -49,27 +49,28 @@ Agents are defined in `.claude/agents/` and invoked via natural language:
 
 ---
 
-## Quick Start
-
-```
-# Set up development environment
-Use the pg-build subagent to help me build Postgres for development
+## Slash Commands
 
-# Run tests after making changes
-Use the pg-test subagent to run regression tests
+Quick actions defined in `.claude/commands/`:
 
-# Before submitting - check readiness
-Use the pg-readiness subagent to evaluate my patch
+| Command | Description |
+|---------|-------------|
+| `/pg-ready` | Check if patch is ready for submission |
+| `/pg-submit` | Prepare patch and draft submission email |
+| `/pg-respond` | Help respond to reviewer feedback |
 
-# Create the patch
-Use the pg-patch-create subagent to prepare my changes
+---
 
-# Write the email
-Use the pg-hackers-letter subagent to draft a submission email
+## Quick Start
 
-# After feedback arrives
-Use the pg-feedback subagent to address the review comments
 ```
+/pg-ready      # Check if patch is ready
+/pg-submit     # Prepare patch + draft email
+/pg-respond    # Address reviewer feedback
+```
+
+For detailed help, invoke agents via natural language:
+> "Use the pg-build subagent to help me configure a debug build"
 
 ---