postgres-code-review — Claude Code skill for PostgreSQL reviews
postgres-code-review is a Claude Code skill that checks PostgreSQL queries, schemas, and connection code for issues with indexes, JSONB, pooling, and transactions.
Apache-2.0 158 installs ★ 89 updated 2026-09-15
npx skills add existential-birds/beagle --skill postgres-code-review -a claude-codeWhat postgres-code-review does
The skill checks whether WHERE and JOIN columns have suitable indexes, whether composite index order fits query patterns, and whether JSONB operators and indexes match how the data is queried. It also reviews pool limits, connection release, transaction isolation, and parameterized SQL.
It asks for paths to the code under review before reporting findings. Performance claims need a link to the relevant statement or schema; an injection warning must identify how the code combines SQL and values. The skill then directs the reviewer to a matching file in references/ and the review checklist. Findings need code references, so unsupported conclusions do not pass its gates.
Install with npx skills add existential-birds/beagle --skill postgres-code-review -a claude-code. The skill file is at ~/.claude/skills/postgres-code-review/SKILL.md.
What it helps with
- spot queries that lack suitable indexes
- check JSONB operators and index choices
- find connection leaks or pool configuration issues
- review transaction isolation and possible deadlocks
- check whether SQL values use bound parameters
Example prompts for the agent
- Review these queries and migrations for indexing problems.
- Check the JSONB operators and indexes used here.
- Inspect connection handling and transactions for leaks or deadlocks.
How to install postgres-code-review
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill postgres-code-review -a claude-code2Manually: put the files in place
~/.claude/skills/postgres-code-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/postgres-code-review/
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill postgres-code-review -a codex2Manually: put the files in place
.agents/skills/postgres-code-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill postgres-code-review -a cursor2Manually: put the files in place
.cursor/skills/postgres-code-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install existential-birds/beagle plugins/beagle-python/skills/postgres-code-review2Manually: put the files in place
.github/skills/postgres-code-review/SKILL.md1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill postgres-code-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/existential-birds/beagle --path plugins/beagle-python/skills/postgres-code-reviewManually: put the files in place
.devin/skills/postgres-code-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill postgres-code-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about postgres-code-review
How do I install postgres-code-review in Claude Code?
Run npx skills add existential-birds/beagle --skill postgres-code-review -a claude-code. The skill file is located at ~/.claude/skills/postgres-code-review/SKILL.md.
What does postgres-code-review do?
It reviews PostgreSQL SQL, schemas, and connection code. It checks indexes, JSONB usage, query parameterization, and transaction handling.
How does the skill support performance findings?
Index, sequential-scan, and JSONB findings must point to the relevant SQL statement or schema. An SQL-injection warning must identify how the code combines the query and its values.
Source text
SKILL.md · Apache-2.0
--- name: postgres-code-review description: Reviews PostgreSQL code for indexing strategies, JSONB operations, connection pooling, and transaction safety. Use when reviewing SQL queries, database schemas, JSONB usage, or connection management. --- # PostgreSQL Code Review ## Quick Reference | Issue Type | Reference | |------------|-----------| | Missing indexes, wrong index type, query performance | [references/indexes.md](references/indexes.md) | | JSONB queries, operators, GIN indexes | [references/jsonb.md](references/jsonb.md) | | Connection leaks, pool configuration, timeouts | [references/connections.md](references/connections.md) | | Isolation levels, deadlocks, advisory locks | [references/transactions.md](references/transactions.md) | ## Review Checklist - [ ] WHERE/JOIN columns have appropriate indexes - [ ] Composite indexes match query patterns (column order matters) - [ ] JSONB columns use GIN indexes when queried - [ ] Using proper JSONB operators (`->`, `->>`, `@>`, `?`) - [ ] Connection pool configured with appropriate limits - [ ] Connections properly released (context managers, try/finally) - [ ] Appropriate transaction isolation level for use case - [ ] No long-running transactions holding locks - [ ] Advisory locks used for application-level coordination - [ ] Queries use parameterized statements (no SQL injection) ## Gates (before reporting findings) Use this sequence so conclusions stay evidence-bound (not “I checked mentally”): 1. **Scope** — Record the concrete paths (and line ranges or symbols if helpful) for the SQL, DDL/migrations, and connection code under review. **Pass:** every subsystem you critique (queries, JSONB, pool, transactions) has at least one cited path. 2. **SQL/DDL citation for performance claims** — Index, sequential-scan, JSONB-operator, and plan-related findings must point to the exact statement or schema (quoted excerpt or `file:line`). **Pass:** each such finding includes that citation. 3. **Binding check before injection flags** — Only assert SQL-injection risk after locating how SQL and values are combined (bound parameters vs string concat/format/f-strings). **Pass:** you name the mechanism you saw in code for each flagged callsite. Then load the relevant reference doc from [Quick Reference](#quick-reference) and walk the [Review Checklist](#review-checklist). ## When to Load References - Reviewing SELECT queries with WHERE/JOIN → indexes.md - Reviewing JSONB columns or JSON operations → jsonb.md - Reviewing database connection code → connections.md - Reviewing BEGIN/COMMIT or concurrent updates → transactions.md ## Review Questions 1. Will this query use an index or perform a sequential scan? 2. Are JSONB operations using appropriate operators and indexes? 3. Are database connections properly managed and released? 4. Is the transaction isolation level appropriate for this operation? 5. Could this cause deadlocks or long-running locks?
© existential-birds · Apache-2.0 · existential-birds/beagle