perf-analysis

Parse perf.log metrics and create performance-improvement issues.

2|Updated Sep 12, 2012
One-click install
npx skills add https://github.com/jiikko/dotfiles --skill perf-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-analysis
Source: https://github.com/jiikko/dotfiles/tree/main/_claude/skills/perf-analysis
Command: npx skills add https://github.com/jiikko/dotfiles --skill perf-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes the ./tmp/perf.log to identify bottlenecks and automatically create performance-improvement Issues.

Core Features & Use Cases

  • Bottleneck detection: parse duration_ms, cpu_percent, and mem_mb to pinpoint heavy operations.
  • Automated issue creation: generate a new Issue in the issues/ directory with findings and remediation suggestions.
  • Use Case: after a load test, surface long-running operations and assign targeted optimization tasks.

Quick Start

Run /perf-analysis to begin the analysis. It will read ./tmp/perf.log, generate insights, and file issues under issues/.

Frequently Asked Questions about perf-analysis

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

FAQPage Schema
How do I identify bottlenecks in performance logs after a load test?

To identify bottlenecks in performance logs, you can analyze the perf.log file to parse duration_ms, cpu_percent, and mem_mb metrics, pinpointing heavy operations that require optimization.

Can I automatically create issues for performance optimization from a log file?

Yes, you can automatically create performance-improvement issues from a log file by analyzing performance metrics and generating new issues with findings and remediation suggestions in the issues directory.

What metrics are required to analyze performance bottlenecks in load testing scenarios?

Analyzing performance bottlenecks in load testing scenarios requires a parsing workflow that computes duration_ms, cpu_percent, mem_mb, and per-operation metrics to accurately review measurable operations.

How do I generate remediation suggestions for long-running operations?

To generate remediation suggestions for long-running operations, you parse performance logs to surface heavy operations and automatically file targeted optimization tasks with actionable findings.

Do I need a specific log format to detect performance issues automatically?

Yes, detecting performance issues automatically requires a log format located at ./tmp/perf.log that supports parsing workflows to compute duration_ms, cpu_percent, mem_mb, and per-operation metrics.