performance-check

Analyze code paths for N+1 queries, missing indexes, and transaction boundaries.

Updated Feb 4, 2026

Search Tags:#testing #performance #queries #analysis #code-quality #static-analysis #N+1

Ready to run

npx skills add https://github.com/cbemister/claude-code --skill performance-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: performance-check
Source: https://github.com/cbemister/claude-code/tree/main/.claude/skills/performance-check
Command: npx skills add https://github.com/cbemister/claude-code --skill performance-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify performance anti-patterns in codebases and surface potential regressions by combining static analysis with optional runtime checks.

Core Features & Use Cases

Static N+1 and unbounded query detection: Detects patterns that typically cause database bottlenecks.
Missing index and pagination checks: Highlights queries that may miss indexes or lack proper pagination.
Phase-based guidance: Provides a structured workflow from changed file identification to performance verification.
Use Case: Before shipping a data-heavy API endpoint, run this Skill to surface hot paths and recommended fixes.

Quick Start

Use the performance-check skill to scan your recent changes and report potential performance issues.

Frequently Asked Questions about performance-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect N+1 queries and unbounded database queries in my code?▼

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.

What is the best way to check for missing indexes and transaction boundary issues before shipping an API?▼

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.

Can I run performance checks on data-heavy workflows during active development?▼

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.

How do I identify performance regressions in recently changed API routes?▼

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.

Does static analysis cover pagination checks for unbounded queries?▼

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.

When should I use static analysis versus runtime tests for performance verification?▼

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.