skills.rest
antriksh-29
antriksh-29COMMUNITY
Explore all skills by this author →
GitHub

benchmark

Benchmark page load metrics against baselines to detect performance regressions.

Updated Mar 24, 2026
Search Tags:#performance#reporting#benchmark#baseline#ci#web-vitals#browse-daemon
One-click install
npx skills add https://github.com/antriksh-29/reddit-automation --skill benchmark-antriksh-29
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/antriksh-29/reddit-automation/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/antriksh-29/reddit-automation --skill benchmark-antriksh-29

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Performance regressions are hard to detect early in fast-moving codebases. This skill automates end-to-end performance benchmarking on pull requests by running deterministic audits, collecting core web vitals, and surfacing regressions against baselines. ## Core Features & Use Cases

  • Automated metrics collection: TTFB, FCP, LCP, DOM Interactive/Complete, and Full Load across configured pages using a browse daemon.
  • Baseline management and comparison: save, compare, and trend analysis across branches and PRs.
  • Report generation: produces human- and machine-readable reports under .gstack/benchmark-reports and JSON baselines for CI dashboards.
  • Extensibility: integrates with CI pipelines and supports page lists via --pages or --diff. ### Quick Start Invoke by typing /benchmark <url> to start a full audit and generate baselines and comparisons.

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 a CI pipeline?▼

Detect web performance regressions by automating benchmarking audits on pull requests to collect metrics like TTFB, FCP, and LCP, then comparing them against stored baselines to surface deviations early.

What metrics are captured when benchmarking page load performance?▼

Benchmarking page load performance captures TTFB, FCP, LCP, DOM Interactive, DOM Complete, Full Load times, resource timing data, and bundle sizes using a browse daemon for comprehensive analysis.

How do I generate machine-readable performance reports for CI dashboards?▼

Generate machine-readable performance reports by running automated benchmark audits that output structured JSON baselines and comparison files into the .gstack/benchmark-reports directory for CI dashboard integration.

Can I benchmark specific pages instead of an entire multi-page site?▼

Benchmark specific pages by passing a targeted page list via the --pages flag or dynamically selecting pages based on changes using the --diff flag during the audit invocation.

What is the best way to compare performance metrics across pull request branches?▼

The best way to compare performance metrics across branches is to save baseline measurements from the main branch, then run automated audits on PRs to generate structured comparisons and trend analysis.

Does performance benchmarking require external dependencies or browser automation tools?▼

Performance benchmarking relies on a built-in browse daemon for metric collection and requires no external dependencies, enabling deterministic end-to-end audits directly within your existing environment.

Related Skills

Explore More Software Engineering Skills→
MissTullyMissTully

benchmark

Measure and compare web performance metrics across pull requests.

Community
Advanced
ShmurdocShmurdoc

benchmark

Compare web performance metrics against baselines to detect regressions.

Community
Advanced
djkloopdjkloop

optimize

Diagnose and fix UI performance issues in web applications using Lighthouse and bundle analyzers.

Community
Intermediate
yocxy2yocxy2

benchmark

Measure page load times, Core Web Vitals, and resource sizes to detect performance regressions.

Community
Advanced