canary

Monitors a deployed URL for console, performance, and page anomalies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production deployments can silently fail after release. This monitoring workflow watches a live app for console errors, performance regressions, and page failures to surface anomalies early.

Core Features & Use Cases

  • Continuous post-deploy monitoring using a browser-based model to observe console logs, load times, baselines, and visual integrity.
  • Baseline capture and page-level comparisons to detect regressions across a set of pages after deploy.
  • Actionable alerts and guidance for quick triage and rollback decisions.

Quick Start

Run /canary https://example.com to start a 10-minute canary on your production URL.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor a production URL for post-deploy issues?▼

Monitor a production URL for post-deploy issues by running a browser-based canary against the target endpoint. The tool takes screenshots, collects metrics, and observes console logs to surface page failures and visual regressions early.

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

Post-deploy canary monitoring is a reliability technique that watches a live app for console errors, performance drops, and page failures. It captures baseline metrics and compares subsequent page loads against them to detect regressions after release.

Can I compare current page behavior against a captured baseline after release?▼

Yes, you can compare current page behavior against a captured baseline after release. The monitoring workflow captures baseline metrics and screenshots, then compares subsequent page loads to detect performance regressions and visual anomalies.

How do I start a canary monitor on my live app?▼

Start a canary monitor on your live app by running the command with your target URL. This initiates a 10-minute browser-based monitoring session that observes console logs, load times, and page behavior for alerts.

Does post-deploy monitoring work without setting up external alerting infrastructure?▼

Yes, post-deploy monitoring works without external alerting infrastructure. The browser-based monitor directly observes the target URL, compares metrics against baselines, and raises actionable alerts and guidance for triage when regressions appear.

When should I use canary monitoring versus standard uptime checks?▼

Use canary monitoring instead of standard uptime checks when you need to detect silent production failures like console errors, performance regressions, and visual integrity issues. It provides page-level comparisons and actionable alerts for quick rollback decisions.