
Perf Code Paths
Before you fire up a profiler, you need to know where to look. This skill maps out code paths, entrypoints, and likely hot files for a performance scenario so you're not profiling blind. It uses repo-map when available or falls back to grep, then outputs a structured list of candidate files with symbols and evidence for why they matter. Keeps results tight at 10-15 files and sticks to Rust, Java, JS/TS, Go, and Python. Think of it as reconnaissance before the actual profiling work. Saves you from that thing where you profile everything and still miss the obvious bottleneck because you didn't map the call chain first.
- GitHub stars
- 1.7K
- last updated
- May 1, 2026
Install
$ npx -y skills add composiohq/awesome-claude-plugins --skill perf-code-paths --agent claude-codeInstalls into .claude/skills of the current project.
Files
perf-code-paths
Identify likely implementation paths for a performance scenario.
Follow docs/perf-requirements.md as the canonical contract.
Required Steps
- Use repo-map if available; otherwise use grep for entrypoints and handlers.
- List top candidate files/symbols tied to the scenario.
- Include imports/exports or call chains when relevant.
Output Format
keywords: <comma-separated list>
paths:
- file: <path>
symbols: [<symbol1>, <symbol2>]
evidence: <short reason>
Constraints
- Focus only on supported languages (Rust, Java, JS/TS, Go, Python).
- Keep to the most relevant 10-15 files.
Sponsors
Details
- Repository
- github.com/composiohq/awesome-claude-plugins
- Category
- Debugging
- First seen
- Jun 11, 2026
More from composiohq/awesome-claude-plugins
All 23- Developer Growth Analysis
- Frontend Design
- Help
- Perf Investigation Logger
- List Subs
- Mcp Builder
- Pause Subs
- Perf Profiler
- Reflecting On Sessions
- Remove Sub
- Senior Frontend
- Theme Factory
- Perf Theory Gatherer
- Perf Theory Tester
- Unpause Subs
- Add Sub
- Perf Analyzer
- Artifacts Builder
- Perf Baseline Manager
- Perf Benchmarker
- Canvas Design
- Changelog Generator