perf-code-paths
SkillFiles & storageMaps the code paths, entrypoints, and files most likely to matter before profiling a performance issue.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the perf-code-paths skill
About this capability
Use when mapping code paths, entrypoints, and likely hot files before profiling.
What this skill tells your AI
The instructions your AI receives, as published by composio-community/awesome-claude-plugins in perf/skills/code-paths/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 2k
- Forks
- 606
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
perf-code-paths- Source
- github.com/composio-community/awesome-claude-plugins