canary

Monitor live deployments for errors, performance regressions, and failures.

Updated May 11, 2026

Search Tags:#performance #monitoring #alerting #canary #anomaly-detection #browser-daemon #post-deploy

Ready to run

npx skills add https://github.com/wodeh/gstack-kimi --skill canary-wodeh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/wodeh/gstack-kimi/tree/main/canary
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill canary-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring helps teams catch errors, regressions, and page failures before they escalate, by continuously observing live deployments and collecting baselines for comparison.

Core Features & Use Cases

Post-deploy checks that watch console errors, perf regressions, and page failures.
Periodic screenshots with baseline comparisons to detect anomalies.
Alerts and dashboards to verify deployment health during post-release verification and production monitoring.

Quick Start

Enable canary monitoring after deployment to start collecting baselines, take periodic screenshots, and alert on anomalies.

Frequently Asked Questions about canary

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

FAQPage Schema

What is post-deploy canary monitoring and how does it detect performance regressions?▼

Post-deploy canary monitoring continuously watches live apps after deployment to detect errors, performance regressions, and page failures by collecting pre-deploy baselines and comparing periodic screenshots to identify anomalies.

How do I monitor console errors and page failures after a production release?▼

You can monitor production health after release by enabling canary monitoring to watch console errors, track performance regressions, and alert on page failures using pre-deploy baselines and periodic screenshots.

Do I need a browse daemon to run post-release verification on my web application?▼

Yes, post-release verification requires the browse daemon to function, along with periodic screenshots, pre-deploy baselines, and anomaly alerts to properly verify deployment health.

What's the best way to set up anomaly alerts for post-deployment checks?▼

The best way to set up anomaly alerts for post-deployment checks is to enable canary monitoring, which automatically collects pre-deploy baselines, takes periodic screenshots, and triggers alerts when anomalies are detected.

Can I use periodic screenshots as a baseline comparison method for production monitoring?▼

Yes, periodic screenshots with pre-deploy baseline comparisons are used for production monitoring to detect visual and performance anomalies, alerting you to regressions and page failures during post-release verification.