lightrun-slow-execution-diagnosis
Diagnose performance incidents in running services with Lightrun MCP: slow endpoints, latency or SLO regressions, timeouts, deadline-exceeded errors, hangs, and slowness that is intermittent, sporadic, occasional, happens only sometimes, or appears only under load. Use when diagnosing a performance incident; prefer this over lightrun-live-runtime-debugging, including for mixed slow-and-incorrect cases. Use slow-execution snapshots when a duration boundary separates problematic executions; use focused active-path snapshots or call stacks for known hangs that may not reach an end marker. Select the narrowest code section, derive an evidence-based threshold, and correlate captured state with code and telemetry. Use lightrun-live-runtime-debugging for non-performance diagnosis and lightrun-ask-prod for one-off timing, when available; otherwise report the scope gap. Do not use for pull-request review, code changes, setup, deployment, or post-deployment performance validation.
Pinned to revision 4e8964e24a5a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/lightrun-slow-execution-diagnosis/SKILL.md
- skills/lightrun-slow-execution-diagnosis/assets/lightrun-small.svg
- skills/lightrun-slow-execution-diagnosis/assets/lightrun.png
- skills/lightrun-slow-execution-diagnosis/references/mcp-tool-discovery.md
- skills/lightrun-slow-execution-diagnosis/references/slow-execution-snapshot-workflow.md
Every link opens the file at its source, pinned to the revision this page describes.