performance-audit

Audits full-stack application performance across 12 dimensions with scored findings and prioritized optimization roadmaps.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill performance-audit-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-audit
Source: https://github.com/greglas75/zuvo/tree/main/skills/performance-audit
Command: npx skills add https://github.com/greglas75/zuvo --skill performance-audit-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often suspect their application is slow but lack a structured, evidence-based way to find bottlenecks across rendering, bundles, APIs, databases, memory, and runtime behavior. This Skill replaces guesswork with a measured, scored audit that produces Impact Models and a prioritized fix roadmap. ## Core Features & Use Cases - 12-Dimension Analysis: Scores rendering, bundle size, assets, API/network, algorithms, memory, database, caching, framework patterns, Web Vitals, backend runtime, and concurrency. - Evidence-Based Findings: Every HIGH/MEDIUM finding carries an Impact Model with estimated savings, blast radius, effort, and confidence tier, plus a file:line citation. - Stack-Adaptive Profiles: Detects Next.js, React, NestJS, FastAPI, Django, PHP (Yii2/Laravel/Symfony), Prisma, and more, then activates the right dimensions and stack-specific checks. - Use Case: Before a major release, run a full audit to catch an N+1 query in a hot path, a 600 KB bundle, and missing cache headers, then follow the generated quick-wins roadmap to fix them in priority order. ## Quick Start Ask the AI to run a full performance audit on the current project, or scope it with a path, file, or a flag like --frontend, --backend, --db, or --bundle.

Frequently Asked Questions about performance-audit

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

FAQPage Schema
How do I run a performance audit on my codebase?

Invoke the audit with no arguments for a full 12-dimension scan, or pass a path or file to scope it. Flags like --frontend, --backend, --db, or --bundle restrict analysis to specific dimension groups.

What performance problems does a full-stack audit detect?

It detects N+1 and unbounded database queries, oversized bundles, sync I/O on the event loop, memory leaks, missing cache headers, request waterfalls, O(n^2) algorithms, and poor Web Vitals. Each finding includes an Impact Model with estimated savings and effort.

Does the performance audit support frameworks like Next.js, FastAPI, or Laravel?

Yes. It detects the stack during Phase 0 and selects a matching profile, activating framework-specific checks for Next.js, React, NestJS, FastAPI, Django, Yii2, Laravel, Symfony, and ORMs like Prisma and SQLAlchemy.

Can I audit only the database or only the frontend?

Yes. Use --db to audit only database queries and schema (D7), --bundle for bundle weight (D2), --frontend for rendering, bundles, assets, and Web Vitals, or --backend for API, algorithms, database, runtime, and concurrency.

Why does the audit report LOW confidence on some findings?

Confidence depends on available tooling. Without a profiler, bundle analyzer, or Lighthouse, the audit runs at PARTIAL or MINIMAL tier where code inspection caps confidence at MEDIUM or LOW, and the report lists prerequisites to upgrade.

When should I not use a performance audit?

Do not use it for code quality review, security analysis, or test coverage assessment, since dedicated review, security-audit, and test-audit workflows cover those. It is also read-only and never modifies source files.