canary

Monitor a live URL for errors, performance regressions, and page failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring helps catch issues in production by watching a live app after deploy. It checks for console errors, performance regressions, and page failures, takes periodic screenshots, and compares results against pre-deploy baselines to raise alerts when anomalies are detected.

Core Features & Use Cases

  • Post-deploy monitoring using the browse daemon to detect console errors, performance regressions, and page failures.
  • Periodic screenshots and baseline comparisons against pre-deploy state with anomaly alerts.
  • Use cases include validating deploys, watching production health, and verifying fixes.

Quick Start

Run the canary with a URL to start monitoring production after deploy.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor production health after a deployment?

Post-deploy production monitoring uses a browser-based canary to continuously watch a live URL for console errors, performance regressions, and page failures. It compares periodic screenshots against pre-deploy baselines to raise alerts when anomalies are detected.

What is post-deploy canary monitoring and how does it work?

Canary monitoring validates production deployments by capturing pre-deploy baselines and then continuously browsing live targeted pages. The browse daemon takes periodic screenshots, checks for console errors, and alerts you when performance regressions or page failures occur.

Can I validate production fixes by watching a live URL for console errors?

Yes, you can validate fixes by running a browser-based canary against a live production URL. It continuously monitors the page for console errors and failures, comparing current state against captured baselines to detect regressions.

Do I need the browse daemon to detect production performance regressions?

Yes, the browse daemon is required to execute the browser-based canary. It drives the continuous monitoring of targeted production pages, captures screenshots, and performs baseline comparisons to detect performance regressions.

How do I configure canary monitoring for specific targeted pages?

You can configure canary monitoring by specifying a live URL, targeted pages, and a configurable duration. The canary captures a pre-deploy baseline and then runs health checks across the specified production pages to detect anomalies.

Why does post-deploy monitoring compare screenshots against a baseline?

Baseline comparisons detect post-deploy anomalies by contrasting live periodic screenshots against the pre-deploy state. This visual and performance regression check ensures that new production changes do not introduce unexpected page failures or errors.