Detect dangerous PostgreSQL migration locks and suggest safer rewrite strategies.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "io.github.cxk280/locksmith" MCP server from askskill: Run: claude mcp add 'io-github-cxk280-locksmith' -- npx -y locksmith-mcp
Please inspect this PostgreSQL migration script, identify operations that may cause long table locks or block writes, and suggest safer rewrites: ALTER TABLE orders ADD COLUMN status TEXT NOT NULL DEFAULT 'new'; CREATE INDEX idx_orders_created_at ON orders(created_at);
Identifies risky locking operations, explains why they are risky, and provides lower-lock alternative rewrites.
I’m deploying this set of database migrations to production. Run a lock-risk preflight check, list issues by severity, and mark which statements should use CONCURRENTLY, be batched, or be split into separate migrations.
Returns a severity-ranked risk list and migration optimization recommendations suitable for production.
Based on the following PostgreSQL migration SQL, summarize unsafe locking patterns and turn them into team guideline recommendations, including preferred patterns and anti-patterns to avoid.
Extracts common dangerous patterns and produces a reusable database migration best-practices checklist.
Get database migration best practices for safe schema changes and zero-downtime releases.
Safely let agents access Postgres, MySQL, and Redis with read-only defaults.
Securely connect AI to PostgreSQL for read-only queries, schema discovery, and performance analysis.
Get PostgreSQL best practices for optimization, schema design, indexing, and security.
Safely explore PostgreSQL schemas and run controlled read or write queries.
Provide local locks, shared state, events, and task queues for AI agents.