perf-code-paths
$
npx mdskill add ComposioHQ/awesome-claude-plugins/perf-code-pathsMap code paths and hot files before profiling.
- Identifies implementation paths for performance scenarios.
- Uses repo-map or grep to find entrypoints.
- Ranks candidates by relevance to the scenario.
- Outputs structured paths with symbols and evidence.
SKILL.md
.github/skills/perf-code-pathsView on GitHub ↗
---
name: perf-code-paths
description: "Use when mapping code paths, entrypoints, and likely hot files before profiling."
version: 1.0.0
---
# 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.
More from ComposioHQ/awesome-claude-plugins
- add-subSubscribe to a skill event. Adds a subscription that injects context before or after a skill runs. Supports optional conditions at both insert-level (inherited by all subscriptions) and subscription-level (AND-stacked). Conditions include fileExists, gitBranch, envSet, envEquals, fileContains (with optional regex).
- helpShow skill-bus overview, status, and available commands. Quick reference for all skill-bus features.
- list-subsList all active skill-bus subscriptions across global and project scopes, showing merge status, insert-level and subscription-level conditions, effective condition stacking, and what would fire for each skill.
- pause-subsTemporarily disable the skill bus. Quick toggle to stop all subscriptions from firing without removing them.
- perf-analyzer"Use when synthesizing perf findings into evidence-backed recommendations and decisions."
- perf-baseline-manager"Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version."
- perf-benchmarker"Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks."
- perf-investigation-logger"Use when appending structured perf investigation notes and evidence."
- perf-profiler"Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence."
- perf-theory-gatherer"Use when generating performance hypotheses backed by git history and code evidence."