Stats
Actions
Tags
From perf
Appends structured perf investigation notes—with exact user quotes, phase summaries, evidence pointers (files/metrics/commands), and decisions—to `{state-dir}/perf/investigations/<id>.md`.
How this skill is triggered — by the user, by Claude, or both
Slash command
/perf:investigation-loggerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Append structured investigation notes to `{state-dir}/perf/investigations/<id>.md`.
Append structured investigation notes to {state-dir}/perf/investigations/<id>.md.
Follow docs/perf-requirements.md as the canonical contract.
## <Phase Name> - <YYYY-MM-DD>
**User Quote:** "<exact quote>"
**Summary**
- ...
**Evidence**
- Command: `...`
- File: `path:line`
**Decision**
- ...
AI_STATE_DIR for state path (default .claude).npx claudepluginhub alamator/claude-plugins --plugin perfAppends structured perf investigation notes—with exact user quotes, phase summaries, evidence pointers (files/metrics/commands), and decisions—to `{state-dir}/perf/investigations/<id>.md`.
Multi-phase performance investigation workflow for establishing baselines, profiling, and making evidence-gated optimization decisions. Use when debugging latency, throughput regressions, or the question "why is this slow?"
Enforces evidence-first debugging for software bugs, incidents, flaky tests, and performance regressions with observation IDs, causality gates, hypothesis tests, and verification rules.