canary

Monitor live production sites for console errors and performance regressions after deployment.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill canary-curielmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/curielmc/beat-SPY --skill canary-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring helps teams catch production issues that slip through CI, by watching live user flows for console errors, performance regressions, and page failures, then comparing against pre-deploy baselines and raising alerts when anomalies are detected.

Core Features & Use Cases

  • Baseline-driven monitoring: Continuously watch a live app after deployment and compare results to pre-deploy baselines.
  • Automated health checks: Capture screenshots, monitor console errors, and measure load times to pinpoint regressions.
  • Telemetry & governance: Record skill usage and outcomes for post-deploy verification and auditing.

Quick Start

Run a canary monitor on the target URL to validate post-deploy health against established baselines.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor live production sites for post-deploy issues?

Post-deploy canary monitoring uses a browser daemon to watch live production sites for console errors, performance regressions, and page failures after deployment. It continuously checks a specified URL and alerts you when anomalies are detected.

What is baseline-driven canary monitoring?

Baseline-driven canary monitoring is a technique that compares live application behavior after deployment against pre-deploy baselines. It captures screenshots, monitors console errors, and measures load times to pinpoint regressions.

How do I catch production console errors and performance regressions that slip through CI?

You can catch production console errors and performance regressions by running automated health checks on a live app after deployment. This process captures screenshots, monitors console errors, and measures load times to pinpoint regressions that CI missed.

Can I specify a duration and page set for post-deploy canary monitoring?

Yes, post-deploy canary monitoring operates on a specified URL with optional duration and page set parameters. This allows you to customize the scope and length of automated health checks against your baseline.

Does post-deploy canary monitoring support telemetry and governance auditing?

Yes, canary monitoring supports telemetry and governance by recording skill usage and outcomes. This provides post-deploy verification data and maintains an audit trail for production health checks.

What is the best way to validate post-deploy health against established baselines?

The best way to validate post-deploy health is to run a canary monitor on the target URL. This compares live production telemetry and browser checks directly against your established pre-deploy baselines.