skills.rest
raghavbadhwar
raghavbadhwarCOMMUNITY
Explore all skills by this author →
GitHub

benchmark

Detects web performance regressions by measuring page metrics against stored baselines.

Updated Aug 9, 2026
Search Tags:#performance#bundle size#benchmark#browser testing#core web vitals#regression detection#page speed
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill benchmark-raghavbadhwar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/raghavbadhwar/rstack/tree/main/benchmark
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill benchmark-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications slow down gradually as each pull request adds small delays and bundle weight, and teams often notice only after load times become unacceptable. This Skill measures page performance continuously, compares results against baselines, and surfaces regressions before they ship. ## Core Features & Use Cases - Baseline Capture and Comparison: Record baseline metrics for page load times, Core Web Vitals, and resource sizes, then compare before and after on every PR. - Detailed Metric Collection: Gather TTFB, FCP, LCP, DOM Interactive, DOM Complete, full load time, resource sizes, and bundle breakdowns via the browse daemon's perf command and JavaScript evaluation. - Trend Tracking and Diff Scoping: Run benchmarks only on pages affected by the current branch with --diff, or review historical performance trends with --trend. - Use Case: Before merging a feature branch, run a diff-scoped benchmark to confirm the changed pages did not regress in load time or JavaScript bundle size compared to the stored baseline. ## Quick Start Ask the agent to run /benchmark against your local dev server URL to capture a performance baseline and audit Core Web Vitals for the page.

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 a pull request?▼

Capture a baseline with /benchmark <url> --baseline before making changes, then run /benchmark <url> after changes to compare. The skill reports differences in load times, Core Web Vitals, and resource sizes so regressions are visible before merge.

How to measure Core Web Vitals like LCP and FCP from the command line?▼

The skill navigates to the page with the browse daemon and evaluates the Performance API in JavaScript, extracting LCP and FCP from PerformanceObserver entries plus navigation timing metrics like TTFB and DOM Complete.

Can I benchmark only the pages changed in my branch?▼

Yes. Run /benchmark --diff to compare the current branch against the base branch using git diff, then benchmark only the affected pages instead of the whole site.

What setup is required before running a web performance benchmark?▼

The skill requires the gstack browse daemon binary. If it is missing, the skill prompts for a one-time build via its setup script, which needs Bun installed; the Bun installer checksum is verified before execution.

Does the benchmark track performance trends over time?▼

Yes. Reports and baselines are stored under .gstack/benchmark-reports, and /benchmark --trend reads historical data to show how page performance metrics evolve across runs.

Related Skills

Explore More Software Engineering Skills→
greencmgreencm
1

benchmark

Detect performance regressions and benchmark page speed for web applications.

Community
Advanced
nexus-substratenexus-substrate
18

performance-optimization

Measure p50/p95 bottlenecks, apply targeted fixes, and verify improvements.

Official
Intermediate
shogo-labsshogo-labs
12

canary

Monitor live web app health via console errors, performance, and page failures.

Official
Advanced
tech-leads-clubtech-leads-club
5.0k

perf-lighthouse

Run Lighthouse audits via CLI or Node API and enforce performance budgets.

Official
Intermediate