Use when mapping code paths, entrypoints, and likely hot files before profiling.
Scanned 2/12/2026
Install to Claude Code
Skills Directorynpx -y skills add avifenesh/awesome-slash --skill perf-code-paths --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Perf Code Paths?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/avifenesh-perf-code-paths)More formats (shields.io, HTML) on the badges page.
---
name: perf-code-paths
description: "Use when mapping code paths, entrypoints, and likely hot files before profiling."
version: 1.0.0
---
# perf-code-paths
Identify likely implementation paths for a performance scenario.
Follow `docs/perf-requirements.md` as the canonical contract.
## Required Steps
1. Use repo-map if available; otherwise use grep for entrypoints and handlers.
2. List top candidate files/symbols tied to the scenario.
3. 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
