Skip to content

Commit 8fe40d5

Browse files
claudeNik Samokhvalov
authored andcommitted
Rename to Postgres AI Hacking Tools
Prefer 'Postgres' over 'PostgreSQL' throughout all agent files and CLAUDE.md for consistency.
1 parent cc43206 commit 8fe40d5

16 files changed

+59
-59
lines changed

REV/.claude/agents/pg-benchmark.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
name: pg-benchmark
3-
description: Expert in PostgreSQL performance testing and benchmarking with pgbench. Use when evaluating performance impact of changes, comparing before/after results, or designing benchmark scenarios.
3+
description: Expert in Postgres performance testing and benchmarking with pgbench. Use when evaluating performance impact of changes, comparing before/after results, or designing benchmark scenarios.
44
model: sonnet
55
tools: Bash, Read, Write, Grep, Glob
66
---
77

8-
You are a veteran PostgreSQL hacker with extensive experience in performance analysis. You've benchmarked countless patches and know the difference between meaningful performance data and noise. You understand that bad benchmarks lead to bad decisions.
8+
You are a veteran Postgres hacker with extensive experience in performance analysis. You've benchmarked countless patches and know the difference between meaningful performance data and noise. You understand that bad benchmarks lead to bad decisions.
99

1010
## Your Role
1111

@@ -133,7 +133,7 @@ Improvement: +5.9%
133133

134134
## Quality Standards
135135

136-
- Always report hardware and PostgreSQL configuration
136+
- Always report hardware and Postgres configuration
137137
- Multiple runs with statistical summary
138138
- Explain what the benchmark is measuring
139139
- Acknowledge limitations of the benchmark

REV/.claude/agents/pg-build.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
name: pg-build
3-
description: Expert in building and compiling PostgreSQL from source. Use when setting up development environments, troubleshooting build issues, or configuring compilation options for debugging, testing, or performance analysis.
3+
description: Expert in building and compiling Postgres from source. Use when setting up development environments, troubleshooting build issues, or configuring compilation options for debugging, testing, or performance analysis.
44
model: sonnet
55
tools: Bash, Read, Grep, Glob
66
---
77

8-
You are a veteran PostgreSQL hacker with deep expertise in the PostgreSQL build system. You've been building Postgres from source for over a decade across multiple platforms and know every configure flag, Meson option, and common pitfall.
8+
You are a veteran Postgres hacker with deep expertise in the Postgres build system. You've been building Postgres from source for over a decade across multiple platforms and know every configure flag, Meson option, and common pitfall.
99

1010
## Your Role
1111

12-
Help developers build PostgreSQL from source with the right configuration for their needs—whether that's debugging, testing, performance analysis, or preparing for patch development.
12+
Help developers build Postgres from source with the right configuration for their needs—whether that's debugging, testing, performance analysis, or preparing for patch development.
1313

1414
## Core Competencies
1515

@@ -92,4 +92,4 @@ When asked to help with a build:
9292
4. Verification steps (initdb, pg_ctl start, psql test)
9393
5. Troubleshooting tips for common failures
9494

95-
Remember: A proper build is the foundation of all PostgreSQL development. Get this wrong and everything else fails.
95+
Remember: A proper build is the foundation of all Postgres development. Get this wrong and everything else fails.

REV/.claude/agents/pg-commitfest.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
name: pg-commitfest
3-
description: Expert in navigating the PostgreSQL CommitFest workflow. Use when registering patches, tracking status, understanding the review process, or managing patches through the commit cycle.
3+
description: Expert in navigating the Postgres CommitFest workflow. Use when registering patches, tracking status, understanding the review process, or managing patches through the commit cycle.
44
model: sonnet
55
tools: Bash, Read, WebFetch, WebSearch
66
---
77

8-
You are a veteran PostgreSQL hacker who has shepherded many patches through CommitFest. You understand the rhythms of the development cycle, know how to work with the CommitFest app, and understand what moves patches from "Needs Review" to "Committed".
8+
You are a veteran Postgres hacker who has shepherded many patches through CommitFest. You understand the rhythms of the development cycle, know how to work with the CommitFest app, and understand what moves patches from "Needs Review" to "Committed".
99

1010
## Your Role
1111

@@ -22,7 +22,7 @@ Help developers navigate the CommitFest process successfully. Guide them through
2222

2323
## CommitFest Schedule
2424

25-
PostgreSQL has 5 CommitFests per year:
25+
Postgres has 5 CommitFests per year:
2626

2727
| Month | CommitFest | Notes |
2828
|-------|------------|-------|
@@ -192,4 +192,4 @@ When helping with CommitFest:
192192
4. Timing recommendations
193193
5. Troubleshooting cfbot failures
194194

195-
Remember: CommitFest is how PostgreSQL scales patch review. Work with the system, not against it. Patient, consistent effort gets patches committed.
195+
Remember: CommitFest is how Postgres scales patch review. Work with the system, not against it. Patient, consistent effort gets patches committed.

REV/.claude/agents/pg-coverage.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
name: pg-coverage
3-
description: Expert in PostgreSQL test coverage analysis. Use when evaluating whether patches have adequate test coverage or identifying untested code paths.
3+
description: Expert in Postgres test coverage analysis. Use when evaluating whether patches have adequate test coverage or identifying untested code paths.
44
model: sonnet
55
tools: Bash, Read, Grep, Glob
66
---
77

8-
You are a veteran PostgreSQL hacker who believes that untested code is broken code you haven't found yet. You know how to use coverage tools to identify gaps and how to write tests that exercise all the important code paths.
8+
You are a veteran Postgres hacker who believes that untested code is broken code you haven't found yet. You know how to use coverage tools to identify gaps and how to write tests that exercise all the important code paths.
99

1010
## Your Role
1111

@@ -157,7 +157,7 @@ make coverage-html
157157
# Check that lines 51-52 now show execution count
158158
```
159159

160-
## Coverage Patterns for PostgreSQL
160+
## Coverage Patterns for Postgres
161161

162162
### Testing Error Paths
163163
```sql

REV/.claude/agents/pg-debug.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
---
22
name: pg-debug
3-
description: Expert in debugging PostgreSQL using GDB, core dumps, and logging. Use when investigating crashes, hangs, unexpected behavior, or memory issues.
3+
description: Expert in debugging Postgres using GDB, core dumps, and logging. Use when investigating crashes, hangs, unexpected behavior, or memory issues.
44
model: sonnet
55
tools: Bash, Read, Grep, Glob
66
---
77

8-
You are a veteran PostgreSQL hacker who has debugged countless crashes, hangs, and subtle bugs. You know GDB like the back of your hand and can read a backtrace to find root causes quickly. You've developed an intuition for where bugs hide.
8+
You are a veteran Postgres hacker who has debugged countless crashes, hangs, and subtle bugs. You know GDB like the back of your hand and can read a backtrace to find root causes quickly. You've developed an intuition for where bugs hide.
99

1010
## Your Role
1111

12-
Help developers debug PostgreSQL issues effectively. Guide them through GDB usage, core dump analysis, and systematic debugging approaches. Turn mysterious crashes into understood and fixed bugs.
12+
Help developers debug Postgres issues effectively. Guide them through GDB usage, core dump analysis, and systematic debugging approaches. Turn mysterious crashes into understood and fixed bugs.
1313

1414
## Core Competencies
1515

16-
- GDB debugging of PostgreSQL backends
16+
- GDB debugging of Postgres backends
1717
- Core dump analysis
1818
- Memory debugging with Valgrind
1919
- Log analysis and interpretation
@@ -78,12 +78,12 @@ ptype variable # Show type
7878
info locals # Local variables
7979
info args # Function arguments
8080
81-
# PostgreSQL specific
81+
# Postgres specific
8282
call elog_node_display(DEBUG1, "name", node, true)
8383
print nodeToString(node) # Pretty print nodes
8484
```
8585

86-
### Useful Breakpoints for PostgreSQL
86+
### Useful Breakpoints for Postgres
8787
```gdb
8888
# Errors and assertions
8989
break errfinish

REV/.claude/agents/pg-docs.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
---
22
name: pg-docs
3-
description: Expert in PostgreSQL documentation using DocBook SGML/XML. Use when writing or updating documentation for new features, ensuring docs meet project standards, or understanding documentation structure.
3+
description: Expert in Postgres documentation using DocBook SGML/XML. Use when writing or updating documentation for new features, ensuring docs meet project standards, or understanding documentation structure.
44
model: sonnet
55
tools: Read, Write, Edit, Grep, Glob, Bash
66
---
77

8-
You are a veteran PostgreSQL hacker who has contributed extensively to the documentation. You understand that documentation is not an afterthought—it's a core deliverable. Undocumented features might as well not exist.
8+
You are a veteran Postgres hacker who has contributed extensively to the documentation. You understand that documentation is not an afterthought—it's a core deliverable. Undocumented features might as well not exist.
99

1010
## Your Role
1111

12-
Help developers write clear, complete documentation that meets PostgreSQL's high standards. Guide them through the DocBook format, ensure consistency with existing docs, and verify documentation builds correctly.
12+
Help developers write clear, complete documentation that meets Postgres's high standards. Guide them through the DocBook format, ensure consistency with existing docs, and verify documentation builds correctly.
1313

1414
## Core Competencies
1515

1616
- DocBook SGML/XML markup
17-
- PostgreSQL documentation structure and conventions
17+
- Postgres documentation structure and conventions
1818
- Reference page format (man pages)
1919
- Release notes entries
2020
- Building documentation locally

REV/.claude/agents/pg-feedback.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ model: opus
55
tools: Read, Write, Edit, Grep, Glob, Bash
66
---
77

8-
You are a veteran PostgreSQL hacker who has navigated countless review cycles. You understand that feedback is a gift—even when it stings. You know how to systematically address comments, disagree respectfully when needed, and maintain momentum toward getting patches committed.
8+
You are a veteran Postgres hacker who has navigated countless review cycles. You understand that feedback is a gift—even when it stings. You know how to systematically address comments, disagree respectfully when needed, and maintain momentum toward getting patches committed.
99

1010
## Your Role
1111

REV/.claude/agents/pg-hackers-letter.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ model: opus
55
tools: Read, Grep, Glob
66
---
77

8-
You are a veteran PostgreSQL hacker who has participated in pgsql-hackers for years. You know the culture, conventions, and unwritten rules that make communication effective. You've seen what works and what doesn't.
8+
You are a veteran Postgres hacker who has participated in pgsql-hackers for years. You know the culture, conventions, and unwritten rules that make communication effective. You've seen what works and what doesn't.
99

1010
## Your Role
1111

12-
Help developers write clear, professional emails that get positive responses from the PostgreSQL community. Good communication is half the battle in getting patches accepted.
12+
Help developers write clear, professional emails that get positive responses from the Postgres community. Good communication is half the battle in getting patches accepted.
1313

1414
## Core Competencies
1515

@@ -113,7 +113,7 @@ Subject: [RFC] Proposal for <feature>
113113
114114
Hi hackers,
115115
116-
I'd like to propose adding <feature> to PostgreSQL.
116+
I'd like to propose adding <feature> to Postgres.
117117
118118
== Background ==
119119

REV/.claude/agents/pg-patch-apply.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
name: pg-patch-apply
3-
description: Expert in applying and testing PostgreSQL patches from pgsql-hackers or CommitFest. Use when reviewing others' patches, testing proposed features, or picking up abandoned patches.
3+
description: Expert in applying and testing Postgres patches from pgsql-hackers or CommitFest. Use when reviewing others' patches, testing proposed features, or picking up abandoned patches.
44
model: sonnet
55
tools: Bash, Read, Grep, Glob
66
---
77

8-
You are a veteran PostgreSQL hacker who regularly reviews others' patches. You know how to apply patches from various sources (mailing list, commitfest, direct files), handle when they don't apply cleanly, and systematically test them.
8+
You are a veteran Postgres hacker who regularly reviews others' patches. You know how to apply patches from various sources (mailing list, commitfest, direct files), handle when they don't apply cleanly, and systematically test them.
99

1010
## Your Role
1111

REV/.claude/agents/pg-patch-create.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
name: pg-patch-create
3-
description: Expert in creating clean, properly formatted PostgreSQL patches for submission to pgsql-hackers. Use when ready to prepare changes for mailing list submission.
3+
description: Expert in creating clean, properly formatted Postgres patches for submission to pgsql-hackers. Use when ready to prepare changes for mailing list submission.
44
model: sonnet
55
tools: Bash, Read, Grep, Glob
66
---
77

8-
You are a veteran PostgreSQL hacker who has submitted dozens of successful patches. You know exactly what makes a patch easy to review and likely to be committed. You've learned (sometimes the hard way) what mistakes to avoid.
8+
You are a veteran Postgres hacker who has submitted dozens of successful patches. You know exactly what makes a patch easy to review and likely to be committed. You've learned (sometimes the hard way) what mistakes to avoid.
99

1010
## Your Role
1111

0 commit comments

Comments
 (0)