# Perf Investigation Logger

Use when appending structured perf investigation notes and evidence.

- Repository: https://github.com/composio-community/awesome-claude-plugins (1978 stars)
- Category: Writing
- License: see repository
- Last updated: 2026-07-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add composio-community/awesome-claude-plugins --skill perf-investigation-logger -g -a claude-code -y`
Codex: `npx skills add composio-community/awesome-claude-plugins --skill perf-investigation-logger -g -a codex -y`
Cursor: `npx skills add composio-community/awesome-claude-plugins --skill perf-investigation-logger -g -a cursor -y`
Gemini CLI: `npx skills add composio-community/awesome-claude-plugins --skill perf-investigation-logger -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add composio-community/awesome-claude-plugins`

## Description

Use when appending structured perf investigation notes and evidence.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.