skills.rest
anilveersingh1308
anilveersingh1308COMMUNITY
Explore all skills by this author →
GitHub

gstack-benchmark

Detect web performance regressions by comparing navigation benchmarks against saved baselines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects performance regressions by measuring real page load behavior and comparing it against a saved baseline so slowdowns do not slip into production unnoticed.

Core Features & Use Cases

  • Baseline capture and comparison: Save a baseline and then compare current metrics on the same pages to quantify deltas per PR.
  • Multi-metric performance audit: Measure navigation timing, rendering milestones, load completion, and resource-level findings to pinpoint what changed.
  • Actionable output: Highlight regressions using defined thresholds and surface the slowest resources with recommendations to guide fixes.
  • Use Case: Before and after a PR that changes routing, assets, or critical UI, run benchmarks against the affected URLs and confirm whether Core Web Vitals or bundle size got worse.

Quick Start

Run: /benchmark https://example.com --baseline to capture a baseline before making changes.

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 before merging code changes?▼

You can detect performance regressions by capturing a baseline before changes, then running benchmarks to compare current page speed and Core Web Vitals metrics against that saved JSON baseline.

How do I benchmark page speed and Core Web Vitals for a specific URL?▼

Benchmarking page speed involves running a command like /benchmark https://example.com --baseline to collect navigation timing, rendering milestones, and resource metrics for the specified URL.

What metrics are included in a Core Web Vitals and bundle size performance audit?▼

A performance audit includes navigation timing, rendering milestones, load completion times, and resource-level findings to pinpoint exactly what changed in page speed or bundle size.

Can I use this benchmarking approach for PR checks on routing and asset changes?▼

Yes, you can run benchmarks against affected URLs before and after a PR that changes routing or assets to confirm whether Core Web Vitals or bundle size metrics have regressed.

How does threshold-based regression classification work for page speed monitoring?▼

Threshold-based regression classification compares current benchmark results against saved baselines using defined thresholds to highlight performance drops and surface the slowest resources with recommendations.

Related Skills

Explore More Data & Analytics Skills→
ScivorScivor

benchmark

Benchmark web page performance by collecting navigation timing and resource metrics.

Community
Advanced
AGIBuildAGIBuild
10

dotnet-ci-benchmarking

Compare BenchmarkDotNet JSON results against GitHub Actions artifact baselines.

Community
Advanced
lailtonjuniorlailtonjunior

Pr Review

Automate pull request reviews to enforce team standards and best practices across Git workflows.

Community
Intermediate
Prompt-or-Die-LabsPrompt-or-Die-Labs
7

lighthouse-ci-integrator

Automate Lighthouse performance testing and assertions in CI/CD workflows.

Official
Intermediate