N+1 Query Detector
IntermediadevelopmentContexto mínimo: 32K
Finds N+1 query patterns in ORM and GraphQL code where a loop or resolver issues one query per record instead of a single batched fetch. Explains why each occurrence happens, rewrites it using eager loading, joins, or a dataloader-style batcher, and suggests a test or query-count assertion to keep the regression from returning.
Casos de uso
- Spotting N+1 queries in ORM model access inside loops
- Adding eager loading or joins to collapse repeated queries
- Introducing a dataloader batcher for GraphQL resolvers
- Writing a query-count assertion to prevent regressions
Prompt de ejemplo
Review this code for N+1 query problems. ``` [paste ORM or GraphQL resolver code here] ``` For each occurrence: explain what triggers the extra queries, estimate how many queries run for N records, rewrite it to a batched or eager-loaded version, and show a test that asserts the query count so this cannot silently regress.
Modelos recomendados
Herramientas compatibles
claude-codecursorkirocontinueany
Modalidades
Entrada: text, code
→Salida: text, code
Skills relacionadas
Autor
OpenModels Community