Database Engineering Suite
The two reviews that stop database mistakes before they get expensive in production. One plans and executes safe migrations — with rollback plans, backfill strategies, and zero-downtime sequencing — so a schema change never takes prod down. The other reviews your schema, queries, and migrations for the engine-specific mistakes that get slow or dangerous at scale: bad table design, missing indexes, N+1 and slow queries, SQL injection, and locking migrations. Together they cover the full database change lifecycle, from design and query review to safe rollout. Built for backend engineers who own the data layer.
Works with every agent that reads SKILL.md — Claude Code, Cursor, Codex CLI, Gemini CLI, GitHub Copilot, Windsurf, OpenClaw, and more.
One payment, lifetime access. 2 skills unlock instantly in your library.
30-day refund guarantee
Instant unlock in your library
Free updates from the creator
What's included
2 skills
Plan, review, and execute safe database migrations with automatic rollback plans, backfill strategies, and zero-downtime sequencing.
Review a database schema, queries, or migration for the mistakes that get expensive in production — bad table design, missing or wrong indexes, slow and N+1 queries, SQL injection, and migrations that lock or break prod. Engine-aware (PostgreSQL, MySQL, SQLite, SQL Server), it runs an ordered review and returns a PASS/REVIEW/BLOCK verdict with prioritized fixes. Schema mistakes are the most expensive kind — this catches them before they ship.
See it in action
You say
Add a status column to the orders table (default 'pending', not null) and an index on orders.created_at. We have ~80M rows and cannot take downtime.
Your agent does
This needs to be split into 3 deploys to stay online:
Deploy 1 - add status as a nullable column (instant, no lock). Deploy 2 - backfill status='pending' in 10k-row batches with a resumable script (provided), then add the NOT NULL constraint using NOT VALID + VALIDATE CONSTRAINT to avoid a full-table lock. Deploy 3 - create the created_at index with CREATE INDEX CONCURRENTLY.
I've generated all three migrations, the batched backfill script, and a matching rollback for each. Estimated index build time at 80M rows: ~6-9 min, no write lock.
How to install
Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.