Detect inefficient SQL query patterns and suggest performance optimizations.
npx skills add https://github.com/Hainrixz/claude-db --skill db-query-patterns
Please help me install this Agent Skill. Skill: db-query-patterns Source: https://github.com/Hainrixz/claude-db/tree/main/skills/db-query-patterns Command: npx skills add https://github.com/Hainrixz/claude-db --skill db-query-patterns
This Skill identifies common query anti-patterns that can lead to performance issues in database operations, helping users optimize their queries and improve database performance.
SELECT *: Identifies queries that fetch all columns, defeating index usage and causing unnecessary load.IN operations.OFFSET pagination and suggests keyset/seek pagination for better performance.Run the db-query-patterns skill on your SQL script to detect query anti-patterns.
High-intent search queries and answers about installing and using this skill.
To detect SQL query anti-patterns, use static analysis to identify inefficient patterns like `SELECT *`, structural N+1 queries, and non-SARGable predicates that cause performance issues. This process requires static analysis and may require runtime verification.
Non-SARGable predicates are query conditions that prevent index usage, severely degrading database performance. Identifying these predicates through static analysis allows you to rewrite conditions and restore efficient index seeks for relational databases.
You can identify structural N+1 queries by analyzing SQL scripts for queries executed within loops. Static analysis detects these patterns and suggests optimizing them with joins or batched `IN` operations to reduce database load.
The best way to audit SQL pagination is to analyze scripts for `OFFSET` pagination usage. Static analysis detects this anti-pattern and suggests implementing `keyset/seek` pagination instead to achieve significantly better database performance.
Yes, you can use static analysis to find queries using `SELECT *` in relational databases. Detecting this anti-pattern helps optimize queries by preventing unnecessary data load and defeating proper index usage.
Static analysis is needed initially to detect inefficient SQL query patterns like non-SARGable predicates and structural N+1 issues. Runtime verification may also be required to confirm the actual database performance impact of these identified anti-patterns.
itou-daikiProvide PostgreSQL best practices for query optimization, indexing, and security.
NotysotyAnalyze SQL queries for performance issues and rewrite them with optimized execution plans.
JayRHaMeasure, profile, and validate performance improvements across Python, Node.js, Go, Java, SQL, and HTTP.
zinohomeAnalyze SQL EXPLAIN plans and recommend index strategies.