perf-investigation-logger

Use when appending structured perf investigation notes and evidence.

677 stars

Best use case

perf-investigation-logger is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when appending structured perf investigation notes and evidence.

Teams using perf-investigation-logger should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/perf-investigation-logger/SKILL.md --create-dirs "https://raw.githubusercontent.com/agent-sh/agentsys/main/.kiro/skills/perf-investigation-logger/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/perf-investigation-logger/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How perf-investigation-logger Compares

Feature / Agentperf-investigation-loggerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when appending structured perf investigation notes and evidence.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

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

Related Skills

perf-profiler

677
from agent-sh/agentsys

Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.

perf-theory-tester

677
from agent-sh/agentsys

Use when running controlled perf experiments to validate hypotheses.

perf-benchmarker

677
from agent-sh/agentsys

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-theory-gatherer

677
from agent-sh/agentsys

Use when generating performance hypotheses backed by git history and code evidence.

perf-analyzer

677
from agent-sh/agentsys

Use when synthesizing perf findings into evidence-backed recommendations and decisions.

perf-baseline-manager

677
from agent-sh/agentsys

Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.

perf-code-paths

677
from agent-sh/agentsys

Use when mapping code paths, entrypoints, and likely hot files before profiling.

maintain-cross-platform

677
from agent-sh/agentsys

Use when preparing releases, validating cross-platform compatibility, or updating installation infrastructure. Meta-skill for maintaining AgentSys's 3-platform architecture.

orchestrate-review

677
from agent-sh/agentsys

Use when user asks to "deep review the code", "thorough code review", "multi-pass review", or when orchestrating the Phase 9 review loop. Provides review pass definitions (code quality, security, performance, test coverage), signal detection patterns, and iteration algorithms.

drift-analysis

677
from agent-sh/agentsys

Use when the user asks about plan drift, reality check, comparing docs to code, project state analysis, roadmap alignment, implementation gaps, or needs guidance on identifying discrepancies between documented plans and actual implementation state.

consult

677
from agent-sh/agentsys

Cross-tool AI consultation. Use when user asks to 'consult gemini', 'ask codex', 'get second opinion', 'cross-check with claude', 'consult another AI', 'ask opencode', 'copilot opinion', or wants a second opinion from a different AI tool.

debate

677
from agent-sh/agentsys

Structured AI debate templates and synthesis. Use when orchestrating multi-round debates between AI tools, 'debate topic', 'argue about', 'stress test idea', 'devil advocate'.