Menu
Diagnose slow queries and add the right indexes — read the query plan, index for filters/joins/sorts, avoid over-indexing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Write a blameless incident postmortem — timeline, impact, root cause, and concrete follow-ups, focused on systems not people.
Write clear, conventional git commit messages — type(scope): summary, imperative mood, a body that explains the why.
Build small, secure container images — pinned base, non-root user, multi-stage builds, no secrets in layers, minimal attack surface.
Control and query Home Assistant through the connector's call_service tool — REST API patterns, common domains, how to find entities before acting.
Design predictable REST APIs — noun resources, correct status codes, pagination, consistent errors, and versioning.
Handle API keys, tokens and passwords safely — store them in the vault, reference by name, never in chat, repo, memory, or code.
| name | sql-index-review |
| description | Diagnose slow queries and add the right indexes — read the query plan, index for filters/joins/sorts, avoid over-indexing. |
| category | Data |
| tags | sql, database, performance, indexing |
A query is slow, or before shipping a query that runs hot.
EXPLAIN (ANALYZE, BUFFERS) (Postgres) / EXPLAIN (MySQL). Look
for Seq Scan / full table scan on big tables, and rows estimated ≫ rows returned.WHERE, JOIN ... ON,
and ORDER BY. A composite index follows the column order of the predicate
(equality columns first, then the range/sort column).INCLUDE (...) in Postgres) — no heap fetch.WHERE (WHERE lower(email)=…) unless you
built a matching expression index — it defeats the index.Add the index that turns the most expensive Seq Scan in your hottest query into an index scan; verify with EXPLAIN before and after.