Menu

Individual skill

performance-rca

0upvotes

Investigates CPU, memory, and contention problems with Grafana Pyroscope profiles via the gcx CLI. Compares affected and baseline workloads, locates changed application stacks, and tests root-cause hypotheses against symptom and change evidence. Use when a service shows high CPU, growing memory, GC pressure, lock contention, or hot functions, when code regressed after a deploy, or when given a suspect service, flame graph, trace, or profiling anomaly report. For profiling setup use pyroscope; for profilecli-based analysis use profilecli-insights.

skills/grafana-lgtm/performance-rca/SKILL.md

Read pinned source

Source commit 8fb72a527961f05e708f53d2a0500709e12d7970

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
307
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Performance RCA

Explain the observed performance problem: which workload changed, which code
path accounts for it, and what evidence supports the mechanism. A hotspot is a
location; an anomaly is a lead; neither alone proves a root cause. Stop at the
strongest supported conclusion, including an inconclusive result. Code changes
and proactive optimization are separate tasks.

## Investigation contract

1. Follow Sections 1–5 in order. Reuse verified evidence from an earlier step
   or referring investigation; do not repeat discovery merely to satisfy the
   sequence. Establish each step's prerequisites before interpreting its result.
2. Fix the context, datasource, UTC windows, selectors, and profile type before
Back to top