canary

Monitor live apps post-deployment for console errors and performance regressions.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill canary-lapagayo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/support/canary
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill canary-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring watches the live app for console errors, performance regressions, and page failures using the browse daemon. Takes periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies.

Core Features & Use Cases

  • Canary monitoring of live apps post deployment with automatic anomaly detection
  • Visual baselining using periodic screenshots against pre-deploy baselines
  • Alerting and reporting when anomalies are detected to speed remediation

Quick Start

Run the canary monitor after a deployment and let Nexus alert you when errors, regressions, or failures appear.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor a live app for post-deploy regressions?

Post-deploy canary monitoring analyzes the live app to detect console errors, performance regressions, and page failures by taking periodic screenshots, comparing them against pre-deploy baselines, and alerting you when anomalies are detected.

What is visual baselining for canary deployments?

Visual baselining uses a browse daemon to take periodic screenshots of production pages and compares them against pre-deploy baselines to catch visual or performance regressions after a new release.

How do I set up post-deploy alerting for page failures?

Post-deploy alerting for page failures requires a browse daemon to periodically screenshot live production pages, compare them against pre-deploy baselines, and trigger alerts when console errors or anomalies are detected.

Does canary monitoring work without a browse daemon?

Canary monitoring requires a browse daemon to take periodic screenshots, compare against pre-deploy baselines, and detect console errors or performance regressions, so it cannot function without this dependency.

When should I use post-deploy canary monitoring?

Post-deploy canary monitoring is needed after deployment scenarios such as watching production pages, validating new releases, and catching regressions across user flows to ensure live app stability.

What is the best way to catch console errors after a production deployment?

The best way to catch console errors after deployment is using post-deploy canary monitoring, which watches the live app through a browse daemon, compares periodic screenshots against baselines, and alerts on detected anomalies.