benchmark

Detect performance regressions by comparing baseline and current metrics across PRs.

Updated Mar 31, 2026

Search Tags:#performance #comparison #benchmark #baseline #web-vitals #page-load #perf-daemon

Ready to run

npx skills add https://github.com/huichen/gstack --skill benchmark-huichen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/huichen/gstack/tree/main/benchmark
Command: npx skills add https://github.com/huichen/gstack --skill benchmark-huichen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams detect performance regressions by establishing baselines for page load times, Core Web Vitals, and resource sizes, and by comparing current runs against historical data to surface regressions early.

Core Features & Use Cases

Baseline capture for pages and resources, including key timing metrics and resource sizes.
Regression and trend detection across PRs, branches, and deployments with per-page reporting.
Historical trend analysis to identify slowdowns over time and actionable recommendations to fix bottlenecks.

Quick Start

Run the /benchmark command with a URL to capture baselines and compare performance across revisions.

Frequently Asked Questions about benchmark

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

FAQPage Schema

How do I detect web performance regressions in my PRs?▼

Detect web performance regressions by capturing baseline metrics and comparing current page load times against historical data to surface slowdowns early in your PRs.

What Core Web Vitals and timing metrics are used for baseline performance comparison?▼

Baseline performance comparison uses deterministic timing metrics such as TTFB, FCP, LCP, and resource sizes collected via in-browser timing and a browse daemon to track page load regressions accurately.

How do I capture a baseline for page load performance and resource sizes?▼

Capture a baseline for page load performance by running the benchmark command with a URL, which records key timing metrics and resource sizes to establish a historical reference for future comparisons.

Can I analyze historical performance trends across branches and deployments?▼

Yes, you can analyze historical performance trends across branches and deployments by storing collected metrics to identify slowdowns over time and receive actionable recommendations to fix bottlenecks.

Does performance benchmarking require any specific dependencies or environment setup?▼

Performance benchmarking requires no external dependencies, relying on a browse daemon and in-browser timing to collect deterministic Core Web Vitals and resource sizes for baseline and regression analysis.