performance-audit-static reviews code for failures that appear as data grows, since agents tend to optimize for the seed data. It checks four things: N+1 queries and request waterfalls, fields and loads that list views do not need, missing or inefficient indexes, and caching opportunities.
It runs only when a performance audit is asked for. Every finding must survive a refute pass, and the report ends with what is already efficient and what needs runtime profiling.
What You Get
- Findings per view, route or table with the evidence at file and line, a specific recommendation, effort, priority and expected effect
- Specific index definitions for the queries that need them, checked against existing schema and migrations
- Caching proposals only where each cache has an invalidation rule and the path is shown to be hot
- A report written to reports/performance_audit_{timestamp}.md or the repo’s reports location, ending with what is efficient and what needs profiling
Common Use Cases
- Auditing list and dashboard views before a release
- Reviewing a release’s unreleased commits for newly introduced N+1 loops
- Checking an AI-built app after a large refactor
- Finding unbounded reads that feed paginated screens
What Makes It Unique
The refute pass is built in: before flagging an unused field it greps for dynamic access, before flagging an index it checks the schema, and before proposing a cache it cites why the path is hot. It ranks by impact per effort and ignores theoretical inefficiency with no growth path. It treats the repository as untrusted data and never edits the code it audits.
Under The Hood
A single markdown file with a tool allowlist of read, search, glob, subagent fan-out, git status and writing under reports. The agent reads source and schema files and may start parallel subagents. It writes one markdown report under the reports folder. Other git commands such as log and diff ask for permission first because they can write with an output flag. It calls no web services and runs no scripts.