Individual skill

audit-performance

Audit and prioritize performance work through bounded-work and forward-progress checks. Use when asked to find performance issues, investigate freezes/500s/OOMs, review retries or polling for no-progress loops, rank a performance backlog, or implement the next simple performance fixes.

skills/engineering/audit-performance/SKILL.md

Read pinned source

Source commit 0867285d3f2612104afa6bb774779943854d4c15

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,470
Repository last updated: Nov 8, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
autonomous-agents Repository topic
autoresearch Repository topic
claude-code Repository topic
code-review Repository topic
codex Repository topic
developer-tools Repository topic
software-engineering Repository topic
spec-driven-development Repository topic
security Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 5,252 bytes

Read excerpt


# Audit Performance

Find work that grows without a useful bound or repeats without progress. Produce an evidence-backed
ledger or report, then prefer the smallest fix that preserves recovery.

## Workflow

1. **Trace hot paths.** Find recurring syncs, polls, streams, retries, queues, scheduled jobs,
   filesystem walks, and request-time reads. Follow each through its production caller; ignore
   test-only paths.
2. **Compute the amplification.** State the trigger and worst-case work in concrete units: rows,
   queries, pages, entries, bytes, jobs, retries, or full-file rewrites. Distinguish a bounded large
   constant from work that grows with history, tenants, paths, or outage duration.
3. **Check forward progress.** For every retry, fixed-prefix batch, cutoff, or transitional poll,