| name | detecting-performance-regressions |
| description | Automatically detect performance regressions in CI/CD pipelines by comparing metrics against baselines. Use when validating builds or analyzing performance trends. Trigger with phrases like "detect performance regression", "compare performance metrics", or "analyze performance degradation". |
| version | 1.0.0 |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(ci:*), Bash(metrics:*), Bash(testing:*) |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| compatible-with | claude-code, codex, openclaw |
| tags | ["performance","ci-cd","detecting-performance"] |
Performance Regression Detector
Detect performance regressions in CI/CD pipelines by comparing response times, throughput, and resource usage against historical baselines using statistical analysis.
Overview
This skill automates the detection of performance regressions within a CI/CD pipeline. It utilizes various methods, including baseline comparison, statistical analysis, and threshold violation checks, to identify performance degradation. The skill provides insights into potential performance bottlenecks and helps maintain application performance.
How It Works
- Analyze Performance Data: The plugin gathers performance metrics from the CI/CD environment.
- Detect Regressions: It employs methods like baseline comparison, statistical analysis, and threshold checks to detect regressions.
- Report Findings: The plugin generates a report summarizing the detected performance regressions and their potential impact.
When to Use This Skill
This skill activates when you need to:
- Identify performance regressions in a CI/CD pipeline.
- Analyze performance metrics for potential degradation.
- Compare current performance against historical baselines.
Examples
Example 1: Identifying a Response Time Regression
User request: "Detect performance regressions in the latest build. Specifically, check for increases in response time."
The skill will:
- Analyze response time metrics from the latest build.
- Compare the response times against a historical baseline.
- Report any statistically significant increases in response time that exceed a defined threshold.
Example 2: Detecting Throughput Degradation
User request: "Analyze throughput for performance regressions after the recent code merge."
The skill will:
- Gather throughput data (requests per second) from the post-merge CI/CD run.
- Compare the throughput to pre-merge values, looking for statistically significant drops.
- Generate a report highlighting any throughput degradation, indicating a potential performance regression.
Best Practices
- Define Baselines: Establish clear and representative performance baselines for accurate comparison.
- Set Thresholds: Configure appropriate thresholds for identifying significant performance regressions.
- Monitor Key Metrics: Focus on monitoring critical performance metrics relevant to the application's behavior.
