mcpField
P
perf-code-paths

perf-code-paths

github.com/composio-communityDevelopment2.0k1.7k installsUpdated 13w ago
Repository

About perf-code-paths

A skill for locating likely implementation paths behind a performance scenario in a code repository. It guides repository searches and limits results to relevant files in supported languages.

Key features

  1. 01Search with repo-map or grep
  2. 02Identify candidate files and symbols
  3. 03Include relevant call chains
  4. 04Limit results to 10–15 files

Use cases

  1. 01Trace code involved in a performance scenario
  2. 02Find entrypoints and handlers for investigation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/composio-community/awesome-claude-plugins --skill perf-code-paths

After installing, type/perf-code-pathsin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported