Skip to content
Skillv1.0.0

detecting-performance-regressions

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 pe

by jeremylongshore(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from jeremylongshore/tons-of-skills-marketplace (plugins/performance/performance-regression-detector/skills/detecting-performance-regressions/SKILL.md). Install upstream with npx skills add jeremylongshore/tons-of-skills-marketplace --skill detecting-performance-regressions. Copyright stays with the author (MIT).

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

  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.

Prerequisites

  • Historical performance baselines in ${CLAUDE_SKILL_DIR}/performance/baselines/
  • Access to CI/CD performance metrics
  • Statistical analysis tools
  • Defined regression thresholds

Instructions

  1. Collect performance metrics from current build
  2. Load historical baseline data
  3. Apply statistical analysis to detect significant changes
  4. Check for threshold violations
  5. Identify specific regressed metrics
  6. Generate regression report with root cause analysis

Output

  • Performance regression detection report
  • Statistical comparison with baselines
  • List of regressed metrics with severity
  • Visualization of performance trends
  • Recommendations for investigation

Error Handling

If regression detection fails:

  • Verify baseline data availability
  • Check metrics collection configuration
  • Validate statistical analysis parameters
  • Ensure threshold definitions are valid
  • Review CI/CD integration setup

Resources

  • Statistical process control for performance testing
  • CI/CD performance testing best practices
  • Regression detection algorithms
  • Performance monitoring strategies

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/jeremylongshore-tons-of-skills-marketplace-detecting-per-fd8600/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

jeremylongshore-tons-of-skills-marketplace-detecting-per-fd8600.ocm.jsonjson
{
  "ocm": "1",
  "id": "jeremylongshore-tons-of-skills-marketplace-detecting-per-fd8600",
  "kind": "skill",
  "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\".",
  "publisher": "jeremylongshore",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "performance",
      "ci-cd",
      "detecting-performance",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "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\"."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/jeremylongshore/tons-of-skills-marketplace",
      "path": "plugins/performance/performance-regression-detector/skills/detecting-performance-regressions/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/HEAD/plugins/performance/performance-regression-detector/skills/detecting-performance-regressions/SKILL.md",
      "key": "jeremylongshore/tons-of-skills-marketplace/plugins/performance/performance-regression-detector/skills/detecting-performance-regressions/SKILL.md"
    },
    "compatibility": "Designed for Claude Code",
    "allowed_tools": [
      "Read,",
      "Write,",
      "Edit,",
      "Grep,",
      "Glob,",
      "Bash(ci:*),",
      "Bash(metrics:*),",
      "Bash(testing:*)"
    ],
    "license": "MIT"
  },
  "instructions": "# Performance Regression Detector\n\nDetect performance regressions in CI/CD pipelines by comparing response times, throughput, and resource usage against historical baselines using statistical analysis.\n\n## Overview\n\nThis 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.\n\n## How It Works\n\n1. **Analyze Perf",
  "cost": {
    "context_tokens": 942
  }
}

Fetch it by URL: GET /api/v1/registry/jeremylongshore-tons-of-skills-marketplace-detecting-per-fd8600/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.