From database-engineering
Operate the database reliably: pool connections with sane limits, choose the isolation level deliberately (knowing its anomalies), keep transactions short, route replica reads carefully, and test restores — a backup is only real if you've restored it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/database-engineering:db-reliabilityThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A pooler (PgBouncer/built-in) with sized limits — an app opening a connection per request exhausts the DB under load.
A pooler (PgBouncer/built-in) with sized limits — an app opening a connection per request exhausts the DB under load.
Read Committed / Repeatable Read / Serializable each permit different anomalies (non-repeatable read, phantom, write skew). Choose, and handle what you allow.
Long txns hold locks, block vacuum, bloat. Keep the critical section minimal.
Replicas are eventually consistent (route read-after-write carefully). Test the restore + PITR if RPO demands. A backup you've never restored is a hope.
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.