perf-investigation-logger
$
npx mdskill add ComposioHQ/awesome-claude-plugins/perf-investigation-loggerLog structured investigation notes with verbatim quotes and evidence.
- Captures exact user quotes, phase summaries, and decision rationales.
- Stores outputs in state directories following canonical contract rules.
- References files, metrics, and commands as evidence pointers.
- Enforces verbatim quoting without paraphrasing user statements.
SKILL.md
.github/skills/perf-investigation-loggerView on GitHub ↗
---
name: perf-investigation-logger
description: "Use when appending structured perf investigation notes and evidence."
version: 1.0.0
---
# perf-investigation-logger
Append structured investigation notes to `{state-dir}/perf/investigations/<id>.md`.
Follow `docs/perf-requirements.md` as the canonical contract.
## Required Content
1. Exact user quotes (verbatim)
2. Phase summary
3. Decisions and rationale
4. Evidence pointers (files, metrics, commands)
## Output Format
```
## <Phase Name> - <YYYY-MM-DD>
**User Quote:** "<exact quote>"
**Summary**
- ...
**Evidence**
- Command: `...`
- File: `path:line`
**Decision**
- ...
```
## Constraints
- Use `AI_STATE_DIR` for state path (default `.claude`).
- Do not paraphrase user quotes.
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-code-paths"Use when mapping code paths, entrypoints, and likely hot files before profiling."
- 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."