perf-review

To detect N+1 queries and unbounded database reads, review your code diffs for loops triggering repeated database calls and missing pagination limits. This process identifies inefficient data access patterns and recommends eager loading or join-based fixes to prevent performance regressions.

Reviewing API routes for over-fetching and missing schema indexes involves inspecting diffs for oversized selects and unfiltered columns. This technique flags unbounded list queries and checks whether filtered columns require database indexes to optimize query performance.

The best way to catch sequential async work in server components is to audit independent async tasks during task-level code reviews. This approach identifies sequential execution bottlenecks and recommends running independent async operations in parallel for faster response times.

Yes, this performance audit works on data access layers and hot paths without external dependencies. It requires only diff inspection and schema awareness to apply severity scoring and actionable fix guidance directly to API routes and server components.

You should not use an automated performance regression check when you lack schema awareness or diff context for the target code changes. The review mechanism requires inspecting actual diffs and schema structures to accurately score severity and generate actionable fix guidance.

To get prioritized findings with concrete fixes for performance regressions, request a review of the active task's code changes. The review applies severity scoring to identified issues like missing indexes and over-fetching, returning clear handoff recommendations.