Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From perf
Identifies entrypoints, hot files, and code paths in Rust, Java, JS/TS, Go, Python repos using repo-map or grep for performance profiling prep.
How this skill is triggered — by the user, by Claude, or both
Slash command
/perf:code-pathsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Identify likely implementation paths for a performance scenario.
Identify likely implementation paths for a performance scenario.
Follow docs/perf-requirements.md as the canonical contract.
keywords: <comma-separated list>
paths:
- file: <path>
symbols: [<symbol1>, <symbol2>]
evidence: <short reason>
npx claudepluginhub frmoretto/awesome-claude-plugins --plugin perfMaps code paths, entrypoints, and likely hot files before profiling. Outputs candidate files and symbols with evidence for performance scenarios.
Produces a token-budgeted, ranked map of important symbols (functions/classes/types) in a codebase. Useful for onboarding to large repos, before deep-review fan-outs, or when JIT context is needed instead of whole-file dumps.
Maps unfamiliar codebases in phases: structure, entry points, data flow, patterns, landmines. Use before coding in new, inherited, or revisited projects.