benchmark

Benchmark page, API, and build performance and output JSON baselines.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/riftzen-bit/gemini-setup --skill benchmark-riftzen-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/riftzen-bit/gemini-setup/tree/main/skills/benchmark
Command: npx skills add https://github.com/riftzen-bit/gemini-setup --skill benchmark-riftzen-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Benchmark skill helps teams quantify performance by establishing baselines, detecting regressions, and guiding stack comparisons across PRs and deployments.

Core Features & Use Cases

  • Modes: Page Performance, API Performance, Build Performance, and Before/After Comparison to cover frontend, backend, and build pipelines.
  • CI & Collaboration: Integrates with PR workflows to quickly surface performance deltas and SLA compliance.
  • Use Case: Before shipping a change, run benchmarks to verify LCP, TTFB, and build times are within targets.

Quick Start

Run the /benchmark baseline command to save current metrics, then make changes and run /benchmark compare to see deltas.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I detect performance regressions in my CI/CD pipeline?

Performance regression detection in CI/CD pipelines compares current build metrics against saved JSON baselines to identify deltas in page, API, and build performance before deployment.

What is the best way to establish a performance baseline for web applications?

Establishing a performance baseline for web applications involves measuring current page and API metrics using a benchmark command, which records the results as JSON to serve as a reference for future PR comparisons.

Can I measure API latency and page load times before merging a pull request?

You can measure API latency and page load times before merging by running benchmark modes tailored for API and page performance within your PR workflow to verify metrics meet SLA compliance and performance targets.

Does this benchmarking approach work for both frontend and build pipeline metrics?

This benchmarking approach supports frontend and build pipeline metrics through dedicated modes for page, API, and build performance, enabling comprehensive stack comparisons and regression detection.

How do I compare performance metrics before and after a code change?

To compare performance metrics before and after a code change, run a baseline command to save initial metrics, implement your changes, then execute a compare command to output the performance deltas.