perf-pass
Skill0 starsChanged 3 months agoMITView on GitHub
Use when something is slow, a page or endpoint feels heavy, or the user asks where the time goes.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lxsmnsyc/agent-skillstheir own version, first seen Nov 8, 2026
- Alfred-Lau/skillstheir own version, first seen Oct 20, 2026
- ccpowerpack/claude-code-skillstheir own version, first seen Jul 3, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- lxsmnsyc/agent-skills★ 4same name
- Alfred-Lau/skills★ 1same name
- ccpowerpack/claude-code-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- api-docsSkill
- code-reviewSkill
- commit-messageSkill
- debug-loopSkill
- explain-this-fileSkill
- onboarding-mapSkill
- pr-descriptionSkill
- refactor-safelySkill
- security-passSkill
- sql-reviewSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Look for the classic wins in order: N+1 queries, work inside a loop that could be hoisted, missing index, missing cache, serial awaits that …
- Distinctive: line 17
Keep the change only if the improvement is real and larger than the noise.
- Distinctive: line 18
Check correctness after each win, especially around caching and concurrency.
- Distinctive: line 19
Stop when the remaining cost is dominated by something you do not control.
- Distinctive: line 23
No micro optimisation before the dominant cost is fixed.
- Distinctive: line 24
No caching added without an invalidation story.
- Distinctive: line 25
No claim of a speedup without before and after numbers.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Perf pass
Measure, then fix the biggest number. Never optimise on a hunch.
Procedure
- Get a number first: wall clock, p95 latency, bundle size or query time. Write it down as the baseline.
- Identify the workload that matters. Optimising a path nobody hits is wasted effort.
- Profile rather than guess: a profiler, timing around suspect blocks,
EXPLAIN ANALYZE, or the network panel. - Look for the classic wins in order: N+1 queries, work inside a loop that could be hoisted, missing index, missing cache, serial awaits that could be concurrent, oversized payloads.
- Change one thing. Re measure with the same method as the baseline.
- Keep the change only if the improvement is real and larger than the noise.
- Check correctness after each win, especially around caching and concurrency.
- Stop when the remaining cost is dominated by something you do not control.
Rules
- No micro optimisation before the dominant cost is fixed.
- No caching added without an invalidation story.
- No claim of a speedup without before and after numbers.
Output format
Baseline: <metric and how measured>
Hot spots: <ranked list with their share of the time>
Changes: <each with before -> after>
Result: <new metric>
Not worth doing: <bullets and why>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.