Detecting Performance Regressions

foryourhealth111-pixel/detecting-performance-regressions

| 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.

4k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

2583

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill detecting-performance-regressions

What comes with it

14 307 bytes besides the instruction

assets/README.md

references/README.md

scripts/README.md

scripts/analyze_metrics.py

scripts/create_github_comment.py

scripts/generate_report.py

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

6 sections, as written by the author

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

performance-testing for benchmark generation
providing-performance-optimization-advice after the regression is confirmed

How to use it

Copy the folder

Take foryourhealth111-pixel/detecting-performance-regressions from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.