canary

Monitor live production apps for console errors, latency regressions, and page failures.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill canary-amanik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill canary-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy Canary monitoring detects production issues that slip past CI by watching the live production app for console errors, latency regressions, and page failures, and by comparing against pre-deploy baselines.

Core Features & Use Cases

  • Continuous post-deploy health checks using a browser-based watcher to detect errors, performance regressions, and broken pages.
  • Baseline capture and comparison with automated screenshots to alert on anomalies.
  • Use Case: verify a new release in production and quickly identify issues before end users are impacted.

Quick Start

Run a canary session against your URL to monitor production for a fixed duration and collect a baseline.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor my production app for issues after a deployment?

Monitor your production app post-deployment by running an automated browser watcher that checks for console errors, latency regressions, and page failures over a fixed duration to catch issues missed by CI.

Can I capture a baseline before deployment to compare against live production?

Yes, you can capture a pre-deployment baseline of your live app. The watcher compares periodic screenshots and performance metrics against this baseline to trigger alerts on any anomalies.

What is the best way to detect page failures and console errors in production?

The best way to detect page failures and console errors is using a dedicated canary watcher that runs continuous health checks via a browse daemon and alerts you when anomalies occur.

Do I need a browser environment to run post-deploy health checks?

Yes, you need a browse daemon to run these post-deploy health checks. The watcher relies on a browser environment to take periodic screenshots, measure latency, and detect live page failures.

Why does post-deploy monitoring catch issues that CI pipelines miss?

Post-deploy monitoring catches issues CI misses because it watches the live production environment directly, detecting real-time console errors, latency regressions, and broken pages under actual traffic conditions.

Can I use this for ongoing production monitoring or only for immediate post-deploy verification?

You can use it for both immediate post-deploy verification and ongoing production monitoring. The watcher runs continuous health checks across pages, capturing baselines and comparing screenshots to alert on anomalies anytime.