lighthouse-ci-integrator

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

7|2|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill lighthouse-ci-integrator-prompt-or-die-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lighthouse-ci-integrator
Source: https://github.com/Prompt-or-Die-Labs/hyper-forge/tree/main/.claude/skills/lighthouse-ci-integrator
Command: npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill lighthouse-ci-integrator-prompt-or-die-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Lighthouse CI helps teams detect and prevent performance regressions by continuously measuring Core Web Vitals and related quality signals in pull requests and automated pipelines.

Core Features & Use Cases

  • Automated Lighthouse runs in CI/CD: Collects Lighthouse reports for configured URLs on every PR or push, enabling reliable regression detection.
  • Core Web Vitals & quality gating: Enforces performance, accessibility, best practices, and SEO assertions with configurable thresholds and budgets.
  • Trends and history via upload targets: Uploads results to an LHCI server or storage backend so you can track changes over time (desktop + mobile).

Quick Start

Ask your AI to “Set up Lighthouse CI to run desktop and mobile performance checks with Core Web Vitals budgets on every pull request, and upload results to your LHCI server.”

Frequently Asked Questions about lighthouse-ci-integrator

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

FAQPage Schema
How do I catch Lighthouse performance regressions in GitHub Actions?

Catch Lighthouse performance regressions in GitHub Actions by configuring CI jobs to collect Lighthouse reports for configured URLs on every pull request. This automates regression detection by asserting Core Web Vitals thresholds against new code changes.

Can I enforce Core Web Vitals budgets in my CI/CD pipeline?

You can enforce Core Web Vitals budgets in your CI/CD pipeline by applying configurable performance assertions to Lighthouse results. This gates pull requests by checking accessibility, best practices, SEO, and performance metrics against your defined thresholds.

What is Lighthouse CI and when do I need it for performance monitoring?

Lighthouse CI is a process of continuously measuring Core Web Vitals and quality signals in automated pipelines. You need it to track Lighthouse score trends across desktop and mobile scenarios and prevent performance degradations before deployment.

How do I set up lighthouserc files to run desktop and mobile checks?

Set up lighthouserc files by defining URL targets, assertions, and upload targets for your LHCI server. You then configure npm scripts or CI jobs to execute lhci collect or lhci autorun with appropriate desktop and mobile scenarios.

Does Lighthouse CI support uploading results to track score trends over time?

Lighthouse CI supports uploading results to an LHCI server or storage backend. This allows you to track performance changes and Lighthouse score trends over time across both desktop and mobile scenarios.

What are the limitations of using lhci autorun for regression testing?

Using lhci autorun for regression testing requires pre-configured lighthouserc files and accessible target URLs. It does not automatically fix performance issues; it only collects reports and fails CI jobs when metrics breach your configured performance budgets.