Skill Detail

Catch benchmark regressions in pull requests before slowdowns ship with CodSpeed

<p>Use CodSpeed when an agent needs benchmark runs compared in CI and surfaced on pull requests before performance regressions merge.</p>

Code Quality & ReviewMulti-Framework
Code Quality & Review Multi-Framework Security Reviewed
โญ 143 GitHub stars โฌ‡ 234.6k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill catch-benchmark-regressions-in-pull-requests-before-slowdowns-ship-with-codspeed Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
A repository with executable benchmarks or benchmark commands, a CI system such as GitHub Actions, and a CodSpeed account or auth flow for storing and comparing results.
Install & setup
<p>Install the CLI with <code>curl -fsSL https://codspeed.io/install.sh | bash</code> or use the official CodSpeed GitHub Action, authenticate the project, then run <code>codspeed exec</code> for direct command benchmarks or <code>codspeed run</code> to wrap an existing benchmark suite in CI and pull requests.</p>
Author
CodSpeed
Publisher
Company
Last updated
Apr 13, 2026
Quick brief

CodSpeed gives an agent a narrow performance-guard workflow. It can run executable programs or existing benchmark suites, compare the results against a baseline, and report regressions directly in pull-request review flows. That makes it useful when a repository already has benchmarks or can add a few targeted ones, and the team wants performance evidence before merge.

How it works

What this skill actually does

The scope boundary is clear. Invoke it when the agent’s job is benchmark execution and regression detection inside review or CI, not when the user wants a general observability platform, profiling backend, or production telemetry stack. The job-to-be-done is catching code slowdowns before they ship.