Benchmark — Performance Baseline & Regression Detection

Benchmark web page, API, and build metrics against stored JSON baselines.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/samymity/bridge-ventures-backend --skill benchmark-performance-baseline-regression-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Benchmark — Performance Baseline & Regression Detection
Source: https://github.com/samymity/bridge-ventures-backend/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/samymity/bridge-ventures-backend --skill benchmark-performance-baseline-regression-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams detect and quantify performance regressions by measuring key user-facing and system metrics before and after code changes.

Core Features & Use Cases

  • Page Performance (Core Web Vitals): Measures browser-based metrics (LCP, CLS, INP, FCP, TTFB) plus page weight, bundle size, and resource/render-blocking signals to catch UX slowdowns.
  • API Performance (Latency & Payload): Benchmarks API endpoints by sampling latency percentiles (p50/p95/p99), response sizes, status codes, and load behavior to validate SLA targets.
  • Build Performance (Dev Feedback Loop): Tracks cold build, hot reload (HMR), tests, TypeScript checks, linting, and Docker build time to prevent developer-experience slowdowns.
  • Before/After Comparison: Saves a baseline and generates a verdict table (including warning/better signals) to make PR impact obvious for both web and backend work.

Quick Start

Run the benchmark baseline, make your changes, then run the comparison to see metric deltas and verdicts.

Frequently Asked Questions about Benchmark — Performance Baseline & Regression Detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect performance regressions in my web application before merging code?

Detect performance regressions by measuring page load and API metrics, comparing them against stored JSON baselines to generate a verdict table for pre-PR verification. You establish a baseline, make changes, then run a comparison to see metric deltas.

What is the best way to track Core Web Vitals changes during CI builds?

Tracking Core Web Vitals during CI builds involves executing browser benchmarks for LCP, CLS, INP, FCP, and TTFB, then persisting results under .ecc/benchmarks/ for CI-friendly comparisons against previous baselines. This process catches UX slowdowns automatically.

How do I benchmark API latency percentiles for SLA validation?

Benchmark API latency for SLA validation by sampling endpoint response times to measure p50, p95, and p99 percentiles, response sizes, and status codes. Comparing these API benchmarks against stored baselines verifies if load behavior meets SLA targets.

Can I measure build metrics like cold build and hot reload time to prevent developer experience slowdowns?

Yes, you can measure build metrics by tracking cold build, hot reload (HMR), tests, TypeScript checks, linting, and Docker build time. Benchmarking these build stages prevents developer-experience slowdowns by comparing results to historical baselines.

Does performance benchmarking work for post-change validation and release readiness?

Performance benchmarking works for post-change validation and release readiness by establishing performance targets and generating before/after comparison tables. This catches subjective 'feels slow' issues by quantifying metric deltas with warning or better signals.