skills.rest
adamtpang
adamtpangCOMMUNITY
Explore all skills by this author →
Website𝕏@adamtpangGitHub

benchmark

Detects web performance regressions by measuring page load metrics and comparing against baselines.

Updated Jun 16, 2026
Search Tags:#performance#monitoring#web vitals#bundle size#benchmark#regression detection#page speed
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill benchmark-adamtpang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/adamtpang/summon.company --skill benchmark-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications slow down gradually as each pull request adds small delays and larger bundles, and teams often notice only after users complain. This Skill measures page performance continuously, captures baselines, and flags regressions before they ship. ## Core Features & Use Cases - Performance Auditing: Collects TTFB, FCP, LCP, DOM timings, and full load times from live pages using the browse daemon's perf command. - Baseline Comparison: Captures pre-change baselines and compares before/after metrics on every PR to detect regressions. - Resource & Bundle Analysis: Breaks down resource sizes, script and CSS transfer sizes, and network request summaries per page. - Use Case: Before merging a feature branch, run a diff-scoped benchmark to verify that only affected pages changed and that none exceeded their performance budgets. ## Quick Start Ask the AI to run a performance benchmark on your local dev server URL and compare the results against the stored baseline.

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

Capture a baseline with the --baseline flag before making changes, then run the benchmark again on your branch. The skill compares TTFB, FCP, LCP, and load times against the baseline and reports regressions per page.

How to measure Core Web Vitals from the command line?▼

The benchmark skill navigates to each page with the browse daemon and evaluates the browser Performance API to extract FCP, LCP, TTFB, and DOM timings. Results are collected as JSON and stored in benchmark reports.

Can I benchmark only the pages affected by my branch?▼

Yes, the --diff flag runs git diff against the base branch to identify changed files and benchmarks only the affected pages. This keeps PR checks fast on large sites.

What setup does the browse daemon need before benchmarking?▼

The browse binary requires a one-time build via the skill's setup script, which takes about ten seconds. If bun is missing, the setup installs it with a checksum-verified install script.

Does the benchmark track performance trends over time?▼

Yes, the --trend flag reads historical benchmark reports stored in .gstack/benchmark-reports to show how metrics evolve across runs. Baselines are kept in a dedicated baselines subdirectory.

Related Skills

Explore More Software Engineering Skills→
GGEduGGEdu

canary-watch

Monitor deployed URLs to detect HTTP, performance, and content regressions.

Community
Intermediate
NAMEWTANAMEWTA
2

performance-optimization

Diagnose and fix frontend and backend performance bottlenecks using measurement-driven workflows.

Community
Intermediate
iamzifeiiamzifei
799

money-product

Automate end-to-end product building and deployment with Stripe payments and canary monitoring.

Community
Advanced
ChegginCheggin
1

performance-benchmark

Measure and enforce web performance budgets with Lighthouse CI.

Community
Advanced