Skip to content

foryourhealth111-pixel/Vibe-Skills / bundled/skills/detecting-performance-regressions

detecting-performance-regressions

Verified

Compare current benchmark results against historical baselines to spot performance regressions. Use as an explicit/manual helper for build-to-build degradation review, not for broad optimization strategy or low-level profiling ownership.

FileKindSize
SKILL.mdskill md1.4 KB
assets/README.mdmarkdown384 B
references/README.mdmarkdown526 B
scripts/README.mdmarkdown631 B
scripts/analyze_metrics.pyscript4.9 KB
scripts/create_github_comment.pyscript3.8 KB
scripts/generate_report.pyscript3.8 KB
---
name: detecting-performance-regressions
description: |
  Compare current benchmark results against historical baselines to spot performance regressions.
  Use as an explicit/manual helper for build-to-build degradation review, not for broad optimization strategy or low-level profiling ownership.
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>
---
# Performance Regression Detector

## Positioning

Treat this skill as an explicit/manual helper for benchmark comparison work.

## When to Use

Use this skill when:
- Identify performance regressions in a CI/CD pipeline.
- Analyze performance metrics for potential degradation.
- Compare current performance against historical baselines.

## Not For / Boundaries

- Broad optimization roadmap or tuning backlog: use `providing-performance-optimization-advice`
- Root-cause debugging of a specific slow path: use `systematic-debugging`
- General test artifact packaging without regression judgment: use `generating-test-reports`

## Typical Outputs

- A baseline-vs-current regression summary
- Severity-ranked regressed metrics
- Follow-up questions for deeper profiling or investigation

## Related Skills

- `performance-testing` for benchmark generation
- `providing-performance-optimization-advice` after the regression is confirmed
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall