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.
npx -y skills add composiohq/awesome-claude-plugins --skill perf-code-paths --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
JamieMason/syncpack
github/awesome-copilot
addyosmani/agent-skills