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.
55
Quality
63%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./bundled/skills/detecting-performance-regressions/SKILL.mdPerformance 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-testingfor benchmark generationproviding-performance-optimization-adviceafter the regression is confirmed
- Repository
- foryourhealth111-pixel/Vibe-Skills
- Commit
f627ab5
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.