perf-investigation-logger

Append structured performance investigation notes to per-incident Markdown files.

1.9k|545|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-plugins --skill perf-investigation-logger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-investigation-logger
Source: https://github.com/ComposioHQ/awesome-claude-plugins/tree/main/perf/skills/investigation-logger
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-plugins --skill perf-investigation-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps teams document structured performance investigation notes and attach evidence in a standardized per-incident file. It ensures quotes, phase summaries, decisions, and pointers to evidence are captured consistently.

Core Features & Use Cases

  • Standardized logging: Append phase-by-phase investigation notes and evidence to a single file located under the AI state directory.
  • Verbatim quoting & structured sections: Enforce verbatim user quotes and a consistent phase/decision/evidence structure for each incident.
  • Use Case: When investigating a perf incident, capture user quotes, phase summaries, decisions, and file/command pointers to evidence in {state-dir}/perf/investigations/<id>.md.

Quick Start

Append a new investigation entry to {state-dir}/perf/investigations/<id>.md following the format defined in docs/perf-requirements.md.

Frequently Asked Questions about perf-investigation-logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document performance investigation notes with evidence in a structured format?

Structured performance investigation notes are documented by appending entries to a per-incident Markdown file using a canonical phase, summary, evidence, and decision format. This captures verbatim user quotes and evidence pointers consistently throughout the incident workflow.

How do I log verbatim user quotes during a performance incident investigation?

Verbatim user quotes are logged within dedicated sections of the investigation Markdown file. The skill enforces a standardized structure, ensuring each phase entry captures the exact user quote alongside the corresponding summary and evidence pointers.

What is the best way to structure phase-by-phase notes for a performance incident?

The best way to structure phase-by-phase notes is using the canonical '## <Phase Name> - <YYYY-MM-DD>' format. Each entry contains dedicated sections for the User Quote, Summary, Evidence, and Decision, ensuring chronological tracking of the investigation.

Where are performance investigation notes and evidence stored by default?

Performance investigation notes are stored in a per-incident Markdown file located under the AI state directory. The default state path enforced is the .claude directory, with files saved to the perf/investigations/ subfolder using the incident ID.

Do I need any external dependencies to append structured performance investigation notes?

No external dependencies are required to append structured performance investigation notes. The skill operates independently to format and write incident logs, requiring only the designated AI state directory for output file storage.

Can I use this structured logging approach for non-performance incidents?

This structured logging approach is specifically tailored for performance incident workflows. It targets perf incident documentation by embedding phase summaries, decisions, and evidence pointers, making it less suitable for non-performance investigations.