From database-engineering
Tune queries with evidence: read EXPLAIN (ANALYZE, BUFFERS) first, choose the right index type and column order (B-tree/partial/composite/covering/GIN), rewrite to be sargable, kill N+1 at the SQL level, and keep statistics fresh.
How this skill is triggered — by the user, by Claude, or both
Slash command
/database-engineering:query-and-index-tuningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`EXPLAIN (ANALYZE, BUFFERS)` — find seq scans, bad row estimates, expensive sorts/joins. Tune what it shows.
EXPLAIN (ANALYZE, BUFFERS) — find seq scans, bad row estimates, expensive sorts/joins. Tune what it shows.
| Predicate | Index |
|---|---|
| equality / range | B-tree |
| filtered subset | partial |
| multi-column (order by selectivity) | composite |
| avoid heap fetch | covering (INCLUDE) |
| jsonb / full-text | GIN |
Make it sargable (no function on the indexed column), avoid SELECT *, batch don't loop, kill N+1 with a join/IN.
Stale stats cause bad plans — ANALYZE/autovacuum tuning fixes more than another index.
npx claudepluginhub mcorbett51090/ravenclaude --plugin database-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.