canary

Detect post-deployment regressions by comparing Web Vitals and error logs against stored baselines.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill canary-jyhthegreat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/JYHTHEGREAT/jyh-system/tree/main/skills/canary
Command: npx skills add https://github.com/JYHTHEGREAT/jyh-system --skill canary-jyhthegreat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a deployment, teams often miss subtle performance degradations, console errors, or HTTP failures because they lack automated monitoring that compares current metrics against a known good baseline.

Core Features & Use Cases

  • Baseline Capture – Store a reference snapshot of Web Vitals, console messages, and HTTP error statistics for a given project.
  • Regression Detection – Compare live metrics with the stored baseline and issue tiered alerts (CRITICAL, HIGH, MEDIUM, LOW) only when regressions persist.
  • Continuous Monitoring – Optional Cron‑based polling every 60 seconds for up to 7 days, automatically re‑running the check.
  • Fallback Handling – Guides for unauthenticated Vercel or disconnected browser‑devtools MCP, and optional Supabase log integration.
  • Use Cases – Detect performance regressions after a Vercel production release, monitor error spikes in critical micro‑services, or verify that new UI changes don’t introduce console errors.

Quick Start

Execute /canary https://my-app.vercel.app --baseline to store a baseline, then run /canary https://my-app.vercel.app to compare and receive regression alerts.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I detect Web Vitals regressions after a Vercel deployment?

To detect Web Vitals regressions after a Vercel deployment, capture a baseline snapshot of your production URL's metrics, console errors, and HTTP logs. Comparing subsequent live metrics against this stored baseline issues tiered alerts when regressions persist.

Can I automate post-deployment monitoring with cron scheduling?

Yes, you can automate post-deployment monitoring using optional cron scheduling. This enables continuous polling every 60 seconds for up to 7 days, automatically re-running regression checks against your stored Web Vitals baseline for sustained alert generation.

What is the best way to set a baseline for production Web Vitals?

The best way to set a baseline for production Web Vitals is executing a baseline capture command on your target Vercel production URL. This stores a reference snapshot of current metrics, console messages, and HTTP error statistics for later regression comparison.

Do I need browser-devtools and Vercel MCP integrations to monitor console errors?

Yes, you need browser-devtools and Vercel MCP integrations to monitor console errors and HTTP logs. The regression detection relies on these connections to collect live Web Vitals, with fallback handling available for unauthenticated Vercel or disconnected browser-devtools environments.

What types of alerts are generated when detecting post-deployment performance regressions?

Tiered alerts (CRITICAL, HIGH, MEDIUM, LOW) are generated when detecting post-deployment performance regressions. These alerts trigger only when live Web Vitals, console errors, or HTTP failure metrics show persistent degradation compared to the stored baseline.

How does fallback handling work if Vercel MCP is unauthenticated?

Fallback handling for unauthenticated Vercel MCP or disconnected browser-devtools guides you through alternative connection setups. It also supports optional Supabase log integration to ensure your post-deployment Web Vitals and HTTP error monitoring continues functioning.