// Use when mapping code paths, entrypoints, and likely hot files before profiling.
| name | perf-code-paths |
| description | Use when mapping code paths, entrypoints, and likely hot files before profiling. |
| version | 5.1.0 |
Identify likely implementation paths for a performance scenario.
Follow docs/perf-requirements.md as the canonical contract.
keywords: <comma-separated list>
paths:
- file: <path>
symbols: [<symbol1>, <symbol2>]
evidence: <short reason>
Use when generating performance hypotheses backed by git history and code evidence.
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
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.
Use when appending structured perf investigation notes and evidence.
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.