---
name: perf-code-paths
description: "Use when mapping code paths, entrypoints, and likely hot files before profiling."
version: 1.0.0
title: perf-code-paths
canonical_url: https://skilld.dev/gh/composiohq/awesome-claude-plugins/code-paths
last_updated: 2026-09-27T18:58:50.000Z
---

> **Skill from skilld.dev.** Follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install composiohq/awesome-claude-plugins/code-paths`. Install writes the Skill files into the project, so every session loads them.

# 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.