skills.rest
tan-yong-sheng
tan-yong-shengCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack-benchmark

Measure navigation timing and resource usage against baselines to detect performance regressions.

1|1|Updated Mar 5, 2026
Search Tags:#performance#lighthouse#regression#benchmark#web-vitals#page-load#browse-daemon
One-click install
npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-benchmark
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-benchmark
Source: https://github.com/tan-yong-sheng/GrowChat/tree/main/.claude/skills/gstack-benchmark
Command: npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-benchmark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: performance, benchmark, page speed, lighthouse, web vitals, bundle size, load time. (gstack)

Core Features & Use Cases

  • Baseline capture and trend tracking across PRs and pages
  • Per-page timing metrics collection (TTFB, FCP, LCP, DOM, etc.) and resource analysis
  • Automated regression detection with clear recommendations and drift alerts
  • Generate shareable reports and visualizations for stakeholders
  • Use Case: When a PR alters a page, run /benchmark to compare current results against the baseline and identify regressions and hotspots

Quick Start

Run the /benchmark command with a target URL to start a performance audit

Frequently Asked Questions about gstack-benchmark

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

FAQPage Schema
How do I detect web performance regressions in a pull request?▼

To detect web performance regressions in a pull request, run a benchmark command against a target URL to measure navigation timing, resource usage, and bundle sizes against an established baseline. This comparison identifies hotspots and anomalies introduced by code changes.

What is the best way to track Core Web Vitals and page load times over multiple runs?▼

Tracking Core Web Vitals and page load times over multiple runs involves establishing a baseline and performing trend analysis across consecutive runs. This approach detects gradual drift, highlights improvements, and identifies performance anomalies affecting metrics like TTFB, FCP, and LCP.

How does the browse daemon collect performance metrics for web apps?▼

The browse daemon collects performance metrics for web apps by measuring per-page navigation timing and resource usage during a benchmark audit. It gathers data on bundle sizes and Core Web Vitals, comparing the results against historical baselines to generate detailed reports.

Can I generate shareable performance reports and visualizations for stakeholders?▼

Yes, you can generate shareable performance reports and visualizations for stakeholders. After collecting metrics and comparing them against baselines, the benchmarking process produces detailed reports that highlight regressions, improvements, and drift alerts for decision making.

Related Skills

Explore More Software Engineering Skills→
sambersamber
2.9k

golang-benchmark

Design and execute Go benchmarks with b.Loop and benchstat comparisons.

Community
Advanced
petbrainspetbrains
13

frontend-playwright

Identify visual regressions across viewports and interactions before deployment.

Official
Intermediate
yashs33244yashs33244
1

benchmark

Benchmark real page load metrics against stored baselines to detect regressions.

Community
Advanced
alexandervashurinalexandervashurin

benchmark

Measure navigation timing metrics and flag performance regressions against historical baselines.

Community
Advanced