sql-query-optimization
>
Works with
--- name: sql-query-optimization description: > license: MIT --- # SQL Query Optimization ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Analyze SQL queries to identify performance bottlenecks and implement optimization techniques. Includes query analysis, indexing strategies, and rewriting patterns for improved performance. ## When to Use - Slow query analysis and tuning - Query rewriting and refactoring - Index utilization verification - Join optimization - Subquery optimization - Query plan analysis (EXPLAIN) - Performance baseline establishment ## Quick Start **PostgreSQL:** ```sql -- Analyze query plan with execution time EXPLAIN (ANALYZE, BUFFERS, FORMAT JSON) SELECT u.id, u.email, COUNT(o.id) as order_count FROM users u LEFT JOIN orders o ON u.id = o.user_id WHERE u.created_at > NOW() - INTERVAL '1 year' GROUP BY u.id, u.email; -- Check table statistics SELECT * FROM pg_stats WHERE tablename = 'users' AND attname = 'created_at'; ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Analyze Current Performance](references/analyze-current-performance.md) | Analyze Current Performance | | [Common Optimization Patterns](references/common-optimization-patterns.md) | Common Optimization Patterns | | [Query Rewriting Techniques](references/query-rewriting-techniques.md) | Query Rewriting Techniques | | [Batch Operations](references/batch-operations.md) | Batch Operations | ## Best Practices ### ✅ DO - Follow established patterns and conventions - Write clean, maintainable code - Add appropriate documentation - Test thoroughly before deploying ### ❌ DON'T - Skip testing or validation - Ignore error handling - Hard-code configuration values
More Database skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-database-setup
prisma/skills
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
prisma-postgres
prisma/skills
Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db/create-pg/create-postgres, or integrating programmatic provisioning with service tokens or OAuth.

