debugging-orm-queries

N+1 queries occur when an ORM executes one query to fetch parent records, then one query per child record instead of batching. Detect them by analyzing logs for repeated similar queries—this Skill parses logs and flags the pattern, then suggests eager loading or batch fetching to consolidate into fewer queries.

Yes. This Skill translates ORM calls from Node.js frameworks (Sequelize, Prisma, TypeORM), Go ecosystems (GORM, sqlc, sqlx, ent), and Python (SQLAlchemy, Django ORM, Peewee) into equivalent SQL, exposing hidden queries for debugging and optimization.

EXPLAIN reveals query execution plans showing full table scans and sequential operations that slow queries. This Skill interprets EXPLAIN output to pinpoint inefficient operations and missing indexes, then recommends index creation to speed up bottleneck queries.

Capture ORM logs, convert them to SQL using this Skill, run EXPLAIN on the raw queries, and analyze the output for N+1 patterns and missing indexes. The Skill automates conversion and analysis steps, producing actionable optimization recommendations immediately.

Yes. This Skill covers Python ORMs including Django ORM, SQLAlchemy, and Peewee, translating their generated SQL and detecting anti-patterns across the full Python ecosystem.

This Skill detects N+1 queries, missing indexes, and other performance anti-patterns in ORM-generated SQL across Node.js, Go, and Python ORMs, then maps findings back to ORM code for refactoring guidance.