canary

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

2|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/vnmoorthy/Skylog --skill canary-vnmoorthy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/vnmoorthy/Skylog/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/vnmoorthy/Skylog --skill canary-vnmoorthy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy monitoring detects console errors, performance regressions, and page failures in the live app. It watches the production build, captures periodic screenshots, and compares them against pre-deploy baselines to catch regressions early.

Core Features & Use Cases

  • Watches the live app for console errors, performance regressions, and page failures using the browse daemon.
  • Takes periodic screenshots and compares them to pre-deploy baselines to detect visual and performance anomalies.
  • Generates alerts when anomalies are detected and supports use cases like monitor deploy, canary checks, and post-deploy verification.

Quick Start

Execute the canary skill after deployment to begin automated health monitoring of the production environment.

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 console errors and performance regressions after deployment?

To monitor a live app for post-deploy console errors and performance regressions, execute the canary skill after deployment to begin automated health monitoring of the production environment. It uses the browse daemon to watch the live app and capture periodic screenshots.

How does baseline comparison work for post-deploy anomaly detection?

Baseline comparison for anomaly detection works by taking periodic screenshots of the live app and comparing them against pre-deploy baselines. This visual and performance comparison detects regressions early and generates alerts when anomalies are detected.

Do I need the browse daemon to run canary checks in production?

Yes, you need the browse daemon to run canary checks in production. It is required to watch the live app for console errors, performance regressions, and page failures, and to capture the periodic screenshots needed for baseline comparisons.

What is the best way to verify deployment health across environments?

The best way to verify deployment health across environments is to apply post-deploy canary monitoring. It watches the production build, compares periodic screenshots to pre-deploy baselines, and issues real-time anomaly alerts to catch regressions early.

Why does post-deploy canary monitoring take periodic screenshots?

Post-deploy canary monitoring takes periodic screenshots to compare them against pre-deploy baselines. This mechanism detects visual and performance anomalies in the live app, triggering alerts when regressions or page failures are identified.

When should I use canary checks for post-deploy verification?

You should use canary checks for post-deploy verification during deployment and in production to monitor health. It is applied to catch console errors, performance regressions, and page failures early by comparing the live app against pre-deploy baselines.