Awesome-claude-plugins perf-code-paths

Name: perf-code-paths
Author: composiohq

Use when mapping code paths, entrypoints, and likely hot files before profiling.

install

source · Clone the upstream repo

git clone https://github.com/ComposioHQ/awesome-claude-plugins

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/ComposioHQ/awesome-claude-plugins "$T" && mkdir -p ~/.claude/skills && cp -r "$T/perf/skills/code-paths" ~/.claude/skills/composiohq-awesome-claude-plugins-perf-code-paths-e5b895 && rm -rf "$T"

manifest: perf/skills/code-paths/SKILL.md

source content

perf-code-paths

Identify likely implementation paths for a performance scenario.

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.