Skip to main content
affpapa.org
RU EN
skill CX Codex

perf-code-paths — Claude Code skill: setup

This skill maps likely execution paths, entrypoints, and related files for a performance scenario before profiling. Useful when the hot area is unclear.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add composio-community/awesome-claude-plugins --skill perf-code-paths -a claude-code
npx skills add composio-community/awesome-claude-plugins --skill code-paths -a claude-code
Open on GitHub

What perf-code-paths does

The skill takes a performance scenario and connects it to entrypoints, handlers, files, and symbols. It narrows the search before a profiler is run.

It uses repo-map when available; otherwise it searches for entrypoints and handlers with grep. The result contains keywords and candidate paths, with symbols and a short reason for each path. Imports, exports, and call chains are included when they help explain the route through the code.

Supported languages are Rust, Java, JS/TS, Go, and Python. The output stays focused on the most relevant 10-15 files. Check docs/perf-requirements.md first, because it defines the canonical contract. The skill is available for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.

What it helps with

  • trace entrypoints for a performance scenario
  • connect handlers to likely hot files
  • map call chains before profiling
  • select relevant symbols from a repository

Example prompts for the agent

  • Map the code path for a slow application startup and identify the entrypoints.
  • Use repo-map if available, otherwise use grep, then list the relevant files and symbols for profiling.
  • Read docs/perf-requirements.md and return keywords, paths, symbols, and a short reason for each path.

How to install perf-code-paths

1Skills CLI (Vercel)

npx skills add composio-community/awesome-claude-plugins --skill perf-code-paths -a claude-code
npx skills add composio-community/awesome-claude-plugins --skill code-paths -a claude-code

2Manually: put the files in place

~/.claude/skills/code-paths/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/code-paths/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about perf-code-paths

How do I install perf-code-paths in Claude Code?

Run npx skills add composio-community/awesome-claude-plugins --skill perf-code-paths -a claude-code, then run npx skills add composio-community/awesome-claude-plugins --skill code-paths -a claude-code. Finally, check ~/.claude/skills/code-paths/SKILL.md.

What does perf-code-paths do?

It maps a performance scenario to entrypoints, handlers, files, and symbols. The skill returns selected paths with brief evidence before profiling starts.

Which languages does perf-code-paths support?

It supports Rust, Java, JS/TS, Go, and Python. Its output focuses on 10-15 files most closely tied to the scenario.

Similar skills

Everything for Code review and refactoring →
m10-performance actionbook System guidance for agents to optimize Rust code systematically, focusing on profiling and memory allocation control. CX Codex +1 3,600installs rust-profiling mohitmishra786 A skill that walks an agent through Rust profiling: flamegraphs, binary size, monomorphization bloat and Criterion microbenchmarks. CX Codex +1 586installs python-performance-optimization Seth Hobson This skill profiles Python code to locate CPU and memory bottlenecks. Use it when an application responds slowly or consumes too many resources. CX Codex 35,675installs django-perf-review getsentry This skill reviews Django code for N+1 queries, unbounded querysets and missing indexes. Useful before a release or when a page slows down on large tables. CX Codex +1 2,900installs memory-leak-detection aj-geddes A skill for tracking down memory leaks: heap snapshots, profiling and the usual patterns behind growing memory use. CX Codex +1 580installs golang-performance samber Guides AI coding agents through profiling, memory allocation cuts, and CPU optimization in Go projects using a strict measurement-first cycle. CX Codex +1 41,900installs

From the same set8

perf-investigation-logger Appends structured performance investigation notes, quotes, and evidence to project logs. Keeps benchmarks and optimization decisions organized. CX Codex +1 1,600installs perf-theory-tester A skill that keeps perf experiments honest: one change per hypothesis, repeated runs, a recorded verdict. Useful when you need proof that an optimization helped. CX Codex +1 1,500installs perf-profiler Runs profilers against CPU and memory hot paths, captures flame graphs, and records file and line evidence. CX Codex +1 1,600installs perf-theory-gatherer A skill that turns git history and code evidence into up to five hypotheses about a performance problem. CX Codex +1 1,600installs perf-benchmarker Runs benchmarks sequentially under strict duration rules to catch performance regressions and set baseline metrics. CX Codex +1 1,600installs perf-analyzer Turns profiling and experiment results into evidence-backed performance recommendations. Use it when a decision needs a traceable basis. CX Codex +1 1,600installs changelog-generator Turns git history into a user-facing changelog: sorts commits into categories and rewrites developer messages for customers. CX Codex +1 1,500installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor