Initial commit

This commit is contained in:
Zhongwei Li
2025-11-30 08:21:19 +08:00
commit 33ce663b79
8 changed files with 195 additions and 0 deletions

View File

@@ -0,0 +1,15 @@
{
"name": "performance-regression-detector",
"description": "Detect performance regressions in CI/CD pipeline",
"version": "1.0.0",
"author": {
"name": "Claude Code Plugins",
"email": "[email protected]"
},
"skills": [
"./skills"
],
"commands": [
"./commands"
]
}

3
README.md Normal file
View File

@@ -0,0 +1,3 @@
# performance-regression-detector
Detect performance regressions in CI/CD pipeline

View File

@@ -0,0 +1,41 @@
---
description: Detect performance regressions in CI/CD
---
# Performance Regression Detector
Detect performance regressions early in the development cycle through automated testing.
## Detection Methods
1. **Baseline Comparison**: Compare against historical performance data
2. **Statistical Analysis**: Detect statistically significant changes
3. **Threshold Violations**: Check against performance budgets
4. **Trend Analysis**: Identify gradual degradation over time
## Metrics to Monitor
- Response time percentiles (p50, p95, p99)
- Throughput (requests per second)
- Resource utilization (CPU, memory)
- Bundle sizes and load times
- Database query performance
## Process
1. Define performance benchmarks
2. Set up automated performance testing in CI/CD
3. Implement regression detection logic
4. Configure notification and reporting
5. Create remediation workflows
## Output
Provide:
- Performance test suite setup
- Baseline performance data collection
- CI/CD integration configuration
- Regression detection thresholds
- Automated reporting setup
- Pull request comment integration
- Remediation workflow documentation

61
plugin.lock.json Normal file
View File

@@ -0,0 +1,61 @@
{
"$schema": "internal://schemas/plugin.lock.v1.json",
"pluginId": "gh:jeremylongshore/claude-code-plugins-plus:plugins/performance/performance-regression-detector",
"normalized": {
"repo": null,
"ref": "refs/tags/v20251128.0",
"commit": "b4ee3755e6841893c5797a60eb7a382313847003",
"treeHash": "7e81743348b2d8f1ce01987ebc593396aa33b06fbb43489fc0a4964c44e4d900",
"generatedAt": "2025-11-28T10:18:39.946814Z",
"toolVersion": "publish_plugins.py@0.2.0"
},
"origin": {
"remote": "git@github.com:zhongweili/42plugin-data.git",
"branch": "master",
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
},
"manifest": {
"name": "performance-regression-detector",
"description": "Detect performance regressions in CI/CD pipeline",
"version": "1.0.0"
},
"content": {
"files": [
{
"path": "README.md",
"sha256": "998a475c3e3bdf014734ea8d0967a72b413fa5afe460f3e56706a8b46767ac49"
},
{
"path": ".claude-plugin/plugin.json",
"sha256": "8afba49cfb3c10b6598a900f4bbb5435c1138c57c0ea291fa41d57733a4508c1"
},
{
"path": "commands/detect-regressions.md",
"sha256": "1c36eeb613eefb3b8a6bbbfabfe335e3fe806f86257951d13feba71d8adaea1b"
},
{
"path": "skills/performance-regression-detector/SKILL.md",
"sha256": "b74b85dd90091f9070c84277a767b9aa6dae02f937ab689de46a43ae000fe3e0"
},
{
"path": "skills/performance-regression-detector/references/README.md",
"sha256": "43d3b0590a6fce235f72639aa41f29f3d7010f9ab247f2293126809e2f86ade0"
},
{
"path": "skills/performance-regression-detector/scripts/README.md",
"sha256": "de2e28f2c9044da550697fc4cfc65bbd6f432beba9228de6d9d0bb7f37ee1419"
},
{
"path": "skills/performance-regression-detector/assets/README.md",
"sha256": "5e6557a86652882e7efd7700ad528ec931b078d33e2650f7cd5727e0b52e2af6"
}
],
"dirSha256": "7e81743348b2d8f1ce01987ebc593396aa33b06fbb43489fc0a4964c44e4d900"
},
"security": {
"scannedAt": null,
"scannerVersion": null,
"flags": []
}
}

View File

@@ -0,0 +1,54 @@
---
name: detecting-performance-regressions
description: |
This skill enables Claude to automatically detect performance regressions in a CI/CD pipeline. It analyzes performance metrics, such as response time and throughput, and compares them against baselines or thresholds. Use this skill when the user requests to "detect performance regressions", "analyze performance metrics for regressions", or "find performance degradation" in a CI/CD environment. The skill is also triggered when the user mentions "baseline comparison", "statistical significance analysis", or "performance budget violations". It helps identify and report performance issues early in the development cycle.
allowed-tools: Read, Write, Edit, Grep, Glob, Bash
version: 1.0.0
---
## 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
1. **Analyze Performance Data**: The plugin gathers performance metrics from the CI/CD environment.
2. **Detect Regressions**: It employs methods like baseline comparison, statistical analysis, and threshold checks to detect regressions.
3. **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:
1. Analyze response time metrics from the latest build.
2. Compare the response times against a historical baseline.
3. 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:
1. Gather throughput data (requests per second) from the post-merge CI/CD run.
2. Compare the throughput to pre-merge values, looking for statistically significant drops.
3. 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.
## Integration
This skill can be integrated with other CI/CD tools to automatically trigger regression detection upon new builds or code merges. It can also be combined with reporting plugins to generate detailed performance reports.

View File

@@ -0,0 +1,7 @@
# Assets
Bundled resources for performance-regression-detector skill
- [ ] report_template.html: HTML template for generating the performance regression report.
- [ ] example_metrics_data.json: Example JSON data showing the format of performance metrics data expected by the plugin.
- [ ] thresholds.json: Example JSON file showing how to define thresholds for performance metrics.

View File

@@ -0,0 +1,7 @@
# References
Bundled resources for performance-regression-detector skill
- [ ] performance_metrics_guide.md: Detailed documentation on the performance metrics used by the plugin, including their definitions, units, and typical ranges.
- [ ] statistical_analysis_methods.md: Explanation of the statistical methods used to detect performance regressions, such as t-tests and z-scores.
- [ ] cicd_pipeline_integration.md: Guide on integrating the plugin into various CI/CD pipelines (e.g., Jenkins, GitHub Actions, GitLab CI).

View File

@@ -0,0 +1,7 @@
# Scripts
Bundled resources for performance-regression-detector skill
- [ ] analyze_metrics.py: Analyzes performance metrics from CI/CD pipeline output, comparing against baselines and thresholds. Returns a JSON object indicating regressions.
- [ ] generate_report.py: Generates a human-readable report summarizing detected performance regressions, including affected metrics, severity, and potential causes.
- [ ] create_github_comment.py: Creates a comment on a GitHub pull request, highlighting detected performance regressions and linking to the generated report.