canary

Monitor production deployments for console errors, performance regressions, and page failures.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/imonmi/INTER-EDU --skill canary-imonmi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/imonmi/INTER-EDU/tree/main/gstack-main/gstack-main/canary
Command: npx skills add https://github.com/imonmi/INTER-EDU --skill canary-imonmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy monitors detect production-time issues such as console errors, performance regressions, and page failures by watching the live app with a browse daemon. It also takes periodic screenshots, compares them against pre-deploy baselines, and alerts on anomalies, enabling quick remediation after deploy.

Core Features & Use Cases

  • Live production monitoring after deployment using the browse daemon to surface errors and performance changes.
  • Baseline capture and screenshot comparisons to track regressions over time.
  • Flexible page selection, duration, and alerting to fit any release workflow.

Quick Start

Run the canary monitor against your production URL to begin a 10-minute health check after deployment.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor production deployments for console errors and performance regressions?▼

Post-deploy monitoring uses a browse daemon to watch your live production app, capturing pre-deploy baselines and comparing them against live screenshots to detect console errors, performance regressions, and page failures after deployment.

What is the best way to set up post-deploy health checks for a production URL?▼

Run a canary monitor against your production URL to begin a 10-minute health check, which takes periodic screenshots and alerts on anomalies compared against pre-deploy baselines for quick remediation.

How does baseline capture work for detecting page failures after a release?▼

Baseline capture records pre-deploy screenshots and performance metrics, then continuous monitoring compares live production pages against these baselines to surface regressions and trigger alerts based on configurable thresholds.

Can I configure the monitoring duration and page selection for my release workflow?▼

Yes, post-deploy monitoring supports flexible page selection, configurable duration, and customizable alert thresholds to fit any release workflow and monitor specific production pages.

Do I need a browse daemon to run production health checks?▼

Yes, the browse daemon is required to continuously watch the live production app, discover pages, take periodic screenshots, and compare them against baselines to detect anomalies.

What limitations should I consider when using screenshot comparisons for post-deploy monitoring?▼

Screenshot comparison monitoring focuses on visual regressions, console errors, and performance changes in production, relying on a browse daemon and pre-deploy baselines, so dynamic content may require careful threshold configuration to avoid false alerts.