perf-review

Scan codebases for performance anti-patterns in database queries, memory, and concurrency.

1|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/trevorbyrum/claude-skills-suite --skill perf-review
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: perf-review
Source: https://github.com/trevorbyrum/claude-skills-suite/tree/main/skills/perf-review
Command: npx skills add https://github.com/trevorbyrum/claude-skills-suite --skill perf-review

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve?

This Skill proactively identifies and flags common performance anti-patterns in code, preventing slowdowns, crashes, and poor user experiences before they impact production.

Core Features & Use Cases

  • Code Scanning: Analyzes backend, frontend, and database layers for issues like N+1 queries, memory leaks, and inefficient loops.
  • Proactive Auditing: Use before deploys or after sprints to catch performance regressions.
  • Use Case: Before launching a new feature, run this skill to ensure database queries are optimized, frontend components don't cause layout thrashing, and no unbounded memory growth is present.

Quick Start

Run a full performance audit across the entire codebase.

Frequently Asked Questions about perf-review

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

FAQPage Schema
How do I find performance bottlenecks in my codebase before deployment?ā–¼

Run a performance audit to scan for anti-patterns across database queries, memory allocation, algorithmic complexity, and frontend rendering. This identifies N+1 queries, memory leaks, and caching gaps before they impact production.

What causes N+1 queries and how can I detect them in my project?ā–¼

N+1 queries occur when database records are fetched inefficiently in loops. Detect them by running a codebase auditing scan that analyzes your database schema and flags these query anti-patterns alongside memory leaks and caching gaps.

How do I scan frontend code for rendering and memory performance issues?ā–¼

Scan frontend code by auditing for performance anti-patterns like layout thrashing and unbounded memory growth. The analysis targets frontend rendering layers to identify inefficient loops and memory leaks causing poor user experiences.

Do I need to provide schema files for a full code performance review?ā–¼

Yes, providing schema files is required to accurately analyze database queries and detect caching gaps. Full codebase access and project context are also needed to identify algorithmic complexity and memory allocation issues.

When should I run a code performance audit during the development cycle?ā–¼

Run a performance audit proactively before deployments or after sprints to catch regressions. Use it before launching new features to ensure database queries are optimized and no unbounded memory growth is present.