Use this skill to analyse a Perfana performance test run and generate a comprehensive standardised performance test report written directly into Obsidian. Includes automatic cross-source root cause investigation when data sources (Tempo traces, Loki logs, Pyroscope flamegraphs, Dynatrace problems) are connected. Trigger when the user says things like "analyse test run", "generate a Perfana report", "write a performance test report", "create a report for run X", "analyse PerfanaWebshop-acc-loadTest-XXXXX", "report on the latest load test", "find root cause", "why did performance regress", or "investigate regression". Also trigger when the user asks to compare a run to a baseline or summarise test results. Requires Perfana MCP and Obsidian Local REST API.
Trigger a load test against the local perfana-demo stack, wait for Perfana's Adapt engine to complete regression analysis, and output a PASS / REGRESSION / INCONCLUSIVE verdict with root cause attribution to a specific Java method. Use when a developer says "perf review", "check my changes for regressions", "did I introduce a performance regression", "run perf-review cpu/pool/backend/build", or "test my afterburner changes". Two modes: Mode A uses a pre-built demo variant (cpu/pool/backend/baseline); Mode B builds the developer's local afterburner changes via Jib and deploys them. Requires Perfana MCP. Grafana MCP and GitNexus MCP improve root cause depth.