perf-investigation-logger

Append structured performance investigation notes with quotes and evidence pointers.

951|110|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/avifenesh/awesome-slash --skill perf-investigation-logger-avifenesh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: perf-investigation-logger
Source: https://github.com/avifenesh/awesome-slash/tree/main/plugins/perf/skills/perf-investigation-logger
Command: npx skills add https://github.com/avifenesh/awesome-slash --skill perf-investigation-logger-avifenesh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance investigations often lack structured, verifiable notes linking user quotes, phase summaries, and evidence. This Skill provides a canonical format to capture quotes, synthesis, and pointers to logs or files for traceability.

Core Features & Use Cases

  • Structured logging: append per-phase notes including verbatim quotes, summaries, and evidence references.
  • Evidence pointers: capture commands, file paths, and metrics to support conclusions.
  • Use Case: during a performance incident, log the user statements, the phase outcomes, and the supporting evidence to build a reproducible incident report.

Quick Start

Append a new investigation note capturing the user quotes, phase summary, and evidence pointers to the designated state directory.

Frequently Asked Questions about perf-investigation-logger

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

FAQPage Schema
How do I log structured performance investigation notes for an incident?▼

You log structured performance investigation notes by appending verbatim user quotes, phase summaries, decisions, and evidence pointers to a canonical markdown document for full incident traceability.

What is the best way to capture verbatim user quotes during performance debugging?▼

Capturing verbatim user quotes during performance debugging involves using a structured logging format that records exact statements alongside phase outcomes and supporting evidence like file paths and metrics.

How do I build a reproducible performance incident report with evidence pointers?▼

You build a reproducible performance incident report by logging structured notes that link phase summaries to evidence pointers like commands, file paths, and metrics within a canonical markdown document.

Can I use markdown to document performance traces and logs across investigation phases?▼

Yes, you can use markdown to document performance traces and logs by appending structured per-phase notes that include evidence references and verbatim quotes to a designated state directory.

When do I need structured logging for performance investigations?▼

Structured logging for performance investigations is needed when you must link user quotes, phase summaries, and evidence pointers to create verifiable, reproducible incident reports.

What evidence should I include in a performance investigation log?▼

In a performance investigation log, you should include verbatim user quotes, phase summaries, decisions, and evidence pointers such as commands, file paths, and metrics to support conclusions.