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 juliusbrussee/awesome-claude-plugins --plugin perf2plugins reuse this skill
First indexed Jul 14, 2026
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.
Build a ranked, token-budgeted map of the codebase — the top files and their key symbols, ranked by how referenced they are — so you navigate to the right 3 files instead of reading 30. Triggers on "map the repo", "where is X", "how is this codebase laid out", "lay of the land", "I'm new to this repo", or at the start of work in a large/unfamiliar project. A zero-dependency repo-map (Glob + Grep + reference counts) that approximates a code graph; complements Sentinel's architectural map and saves tokens.
Maps unfamiliar codebases in phases: structure, entry points, data flow, patterns, landmines. Use before coding in new, inherited, or revisited projects.