canary

Detect production-breaking issues after code deploys using the browse daemon.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill canary-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/team/canary
Command: npx skills add https://github.com/ajsai47/holyclaude --skill canary-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys frequently pass all CI checks but still break in production due to issues like missing environment variables, stale CDN caches, or database migrations that perform poorly on real user data. This skill automates post-deploy monitoring to catch these failures in the first 10 minutes after shipping, rather than waiting for user reports hours or days later.

Core Features & Use Cases

  • Automated Canary Monitoring: Watches your live production app for console errors, performance regressions, page load failures, and broken links using the browse daemon.
  • Baseline Comparison: Takes periodic screenshots and compares them against pre-deploy baselines to spot visual regressions that automated tests might miss.
  • Severity-Based Alerting: Only alerts on persistent anomalies (not transient network blips) with clear severity levels from critical (page failure) to low (new 404s), so you can prioritize fixes fast.
  • Use Case: After shipping a new feature, run this skill to automatically verify your deploy didn't break existing functionality across your app's key user pages.

Quick Start

Use the canary skill to monitor your production app at https://your-app.com for 10 minutes immediately after you finish deploying your latest changes.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor my web app for post-deploy production issues?

Post-deploy monitoring uses a browse daemon to automatically capture screenshots, collect performance metrics, and check key web pages for console errors or broken links, alerting you to persistent anomalies within minutes of a production deploy.

Why do deploys pass continuous integration but still break in production?

Deploys pass continuous integration but break in production due to missing environment variables, stale CDN caches, or poor database migrations. Post-deploy verification catches these real-world failures by monitoring live key user pages instead of just running test suites.

Can I automatically detect visual regressions after shipping a release?

You can detect visual regressions after shipping by capturing periodic screenshots of your live web application and comparing them against pre-deploy baselines, spotting visual changes that automated tests might miss.

What's the best way to catch performance regressions immediately after a code deploy?

The best way to catch performance regressions after a code deploy is to run an automated canary check that monitors your live production app for 10 minutes, comparing real-time page load metrics and console errors against pre-deploy baselines.

How does automated canary monitoring handle transient network errors?

Automated canary monitoring handles transient network blips by applying severity-based alerting that only alerts on persistent anomalies. It categorizes issues from critical page failures to low-priority new 404s, filtering out temporary network errors.

Do I need to configure a browse daemon for deploy verification?

Yes, deploy verification relies on a browse daemon to access your live production application, capture screenshots, collect performance metrics, and alert on broken links or console errors across key user pages.