perf-code-paths
SolidUse when mapping code paths, entrypoints, and likely hot files before profiling.
AI & Automation 1,844 stars
519 forks Updated yesterday
Install
Quality Score: 80/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# 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.
Details
- Author
- composio-community
- Repository
- composio-community/awesome-claude-plugins
- Created
- 9 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- None
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Solid
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
1,844 Updated yesterday
composio-community Data & Documents Solid
perf-profiler
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
1,844 Updated yesterday
composio-community AI & Automation Solid
perf-analyzer
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
1,844 Updated yesterday
composio-community