# Detecting Performance Regressions

> Detecting Performance Regressions is an Agent Skill for testing & quality published in the foryourhealth111-pixel/Vibe-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

- Skill name: `detecting-performance-regressions`
- Category: [Testing & Quality](https://www.openparable.com/skill/testing-quality/1)
- Source: https://github.com/foryourhealth111-pixel/Vibe-Skills/blob/HEAD/bundled/skills/detecting-performance-regressions/SKILL.md
- Repository: foryourhealth111-pixel/Vibe-Skills (2,381 GitHub stars when collected)

## SKILL.md

# 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

---

Source: https://www.openparable.com/skill/testing-quality/detecting-performance-regressions (OpenParable). Cite the canonical URL above.
