hp-verify

Validates generated Astro homepage code with TypeScript, ESLint, build, and Lighthouse CI checks.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill hp-verify-ohmyhotelco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hp-verify
Source: https://github.com/ohmyhotelco/hare-cc-plugins/tree/main/homepage-plugin/skills/hp-verify
Command: npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill hp-verify-ohmyhotelco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After generating homepage code, you need confidence that it compiles, lints cleanly, builds successfully, and meets performance budgets before moving to code review. This Skill automates that entire quality-gate sequence in one step. ## Core Features & Use Cases - Multi-Gate Verification: Runs TypeScript checks (project references or noEmit), ESLint (with optional canonical config template generation), and a full Astro build, recording pass/fail and error details for each. - Lighthouse CI Auditing: Optionally audits the built site against performance, accessibility, best-practices, and SEO thresholds of 90 when @lhci/cli is installed. - Progress Tracking: Updates per-page progress JSON files with verification results and timestamps, keeping the homepage pipeline state machine consistent. - Use Case: After running hp-gen on a pricing page, invoke this Skill to confirm the page type-checks, lints, builds, and scores above 90 on all Lighthouse categories before requesting a code review. ## Quick Start Run the hp-verify skill on my generated homepage code to check TypeScript, ESLint, the Astro build, and Lighthouse scores.

Frequently Asked Questions about hp-verify

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

FAQPage Schema
How do I verify generated Astro homepage code?▼

Run the hp-verify skill after code generation. It sequentially checks TypeScript compilation, ESLint rules, and the Astro build, then optionally runs Lighthouse CI against the dist output and reports pass/fail per gate.

What quality gates does homepage verification run?▼

It runs four gates: TypeScript (tsc -b or --noEmit depending on tsconfig references), ESLint, astro build, and Lighthouse CI. Each gate records pass/fail status, error counts, and details in the page progress file.

Does the verification work without an ESLint config?▼

Yes, if the eslintTemplate option is enabled it writes a canonical eslint.config.js from the plugin template. If required ESLint dependencies are missing, it displays the pnpm install command and skips linting instead of failing.

What Lighthouse scores are required to pass verification?▼

Lighthouse CI must score at least 90 in Performance, Accessibility, Best Practices, and SEO against the static dist build. If @lhci/cli is not installed, the audit is skipped with an install hint rather than failing.

Why does verification reject my page before generation?▼

Verification requires generated code to exist, including .astro pages, section components, and MarketingLayout. If progress status is still planned, you must run the generation step first before any quality gates can execute.