DB Query Optimizer

The problem

Database performance issues often stay hidden during development because ORM code looks clean despite executing inefficiently. N+1 queries and missing indexes only reveal themselves as catastrophic slowdowns or connection pool exhaustion once your data volume grows in production.

What it does

• Identifies N+1 query patterns in ORM code and provides the exact eager-loading or batching syntax for your specific framework.
• Analyzes EXPLAIN and EXPLAIN ANALYZE output to detect sequential scans and inefficient query plans.
• Flags missing indexes on foreign keys, WHERE clauses, and ORDER BY statements, accounting for composite index column order.
• Detects application-level filtering and pagination bugs that should be handled at the database layer.
• Diagnoses connection pool exhaustion caused by high query volume per request.

Frameworks & tools

Supports Prisma, Sequelize, TypeORM, Django ORM, ActiveRecord, SQLAlchemy, and Eloquent. Works with PostgreSQL, MySQL, and SQLite.

Why this beats prompting it yourself

General LLMs often suggest generic fixes or hallucinate ORM methods that do not exist. This skill uses framework-specific reference patterns to ensure the suggested fix is syntactically correct and actually addresses the underlying execution plan rather than just making the code look better.

Use cases

• Auditing an API endpoint that has become progressively slower as the database grows.
• Refactoring legacy ORM code to eliminate N+1 queries in serializers and view layers.
• Optimizing database performance by analyzing slow query logs and execution plans.
• Troubleshooting intermittent database timeouts and connection pool errors under load.