Analyze web page performance metrics to detect regressions across PR changes.
npx skills add https://github.com/geoffreywoo/clawfable --skill benchmark-geoffreywoo
Please help me install this Agent Skill. Skill: benchmark Source: https://github.com/geoffreywoo/clawfable/tree/main/.claude/skills/gstack/benchmark Command: npx skills add https://github.com/geoffreywoo/clawfable --skill benchmark-geoffreywoo
This skill helps teams baseline, measure, and detect web performance regressions across PR changes using a browser-based performance daemon. It centralizes data collection, comparison against historical baselines, and reporting to keep performance at the forefront of CI.
Run /benchmark <url> to start a performance audit and baseline comparison.
High-intent search queries and answers about installing and using this skill.
You can detect web performance regressions by running a performance audit on modified pages to compare current metrics against historical baselines. This CI-ready workflow analyzes TTFB, FCP, LCP, and DOM timings to surface degradations before merging.
The performance baseline comparison captures per-page metrics including TTFB, FCP, LCP, and DOM timings. It also collects navigation and resource entries to analyze bundle sizes and identify heavy scripts or assets.
Yes, you can analyze bundle sizes and resource loading by collecting resource entries during a browser-based performance audit. This process surfaces heavy scripts and assets that may cause performance degradation.
Yes, the browse daemon is required to execute performance audits and collect navigation and resource entries. It operates as the browser-based performance daemon for gathering baseline JSON data and generating Markdown reports.
You can track web performance trends by capturing baselines across builds and comparing them over time. This trend analysis reveals gradual degradation and highlights opportunities for optimization in metrics like LCP and bundle sizes.
Web performance audit reports are stored as JSON and Markdown files under the .gstack/benchmark-reports directory. This output structure ensures auditability and historical tracking for CI baseline comparisons.
jonkikyCollect navigation timing and resource data to establish performance baselines and detect regressions.
wodehMeasure web page timings and compare them to baselines to detect performance regressions.
softmgAutomate GitHub Actions workflow generation and CI/CD pipeline management.
MFS-codeMeasure page load performance and compare metrics against saved baselines.
