db-query-optimization
DB Query Optimization
Overview
Use this skill to improve query performance based on execution evidence, not intuition.
Scope Boundaries
- Hot-path latency or database CPU/IO usage is query-bound.
- Query plans are unstable across parameter distributions.
- Workload changes expose previously acceptable query anti-patterns.
Core Judgments
- Dominant bottleneck: scan cost, join explosion, sort spill, lock wait, network round trips.
- Rewrite scope: query shape, index changes, schema adjustment, or materialization.
- Plan stability and parameter-sensitivity risk.
- Correctness risk from aggressive rewrite or approximation.
Practitioner Heuristics
- Start from actual execution plans and runtime metrics.
- Optimize the highest-impact query families, not one-off outliers.
- Sargability and predicate selectivity usually dominate early wins.
- Keep optimization readable; opaque SQL hacks create long-term maintenance debt.
Workflow
- Identify high-impact queries by frequency and user/business impact.
- Capture plan/runtime evidence under representative parameters.
- Propose rewrites and access-path changes with expected effects.
- Compare candidates for latency gain versus complexity and risk.
- Roll selected change and monitor plan stability and resource usage.
- Record conditions that should trigger re-optimization.
Common Failure Modes
- Tuning for small dev datasets misleads production behavior.
- Index-only fixes mask poor query shape.
- Query changes improve p50 while degrading tail latency.
Failure Conditions
- Stop when no representative workload evidence is available.
- Stop when optimization changes correctness semantics.
- Escalate when required performance target is unattainable without model changes.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9