agentsclimarketplace

Detecting performance regressions

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

VibeSkills is a general-purpose Skill that automatically routes local Skills and intelligently orchestrates harness workflows.

Install
npx -y skills add foryourhealth111-pixel/Vibe-Skills --skill detecting-performance-regressions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.4 KB, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.