performance-check

Static analysis detects N+1 queries and unbounded database queries by scanning code paths to identify performance anti-patterns causing bottlenecks. It highlights missing pagination and indexes in data-heavy workflows.

The best way to check for missing indexes and transaction boundary issues is running static analysis on API routes. It identifies regression risks by verifying transaction boundaries and surfacing hot paths in changed files prior to deployment.

Yes, you can run performance checks on data-heavy workflows during development. The skill provides phase-based guidance from changed file identification to performance verification, applying optional runtime tests alongside static analysis checks.

You identify performance regressions in changed API routes by applying static analysis to detect anti-patterns like missing indexes and unbounded queries. Optional runtime performance tests further verify potential hot paths and bottlenecks.

Yes, static analysis covers pagination checks for unbounded queries by highlighting queries that may miss indexes or lack proper pagination. It surfaces these database bottlenecks to prevent performance regressions in data-heavy endpoints.

Use static analysis during development to catch N+1 queries and missing indexes in code paths, and apply optional runtime performance tests to verify hot paths. Phase-based guidance structures this workflow from file changes to final verification.