canary

Monitor deployed URLs for console errors, performance regressions, and page failures.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill canary-vertakhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill canary-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canary monitoring after deployment catches production issues before users notice them. It watches the live app for console errors, performance regressions, and page failures, ensuring quick detection and safe rollbacks.

Core Features & Use Cases

  • Continuous post-deploy monitoring using a browser daemon to capture console errors, performance metrics, and page failures.
  • Baseline comparison against pre-deploy state, with optional per-page scope and duration.
  • Automatic alerting when anomalies are detected and a quick-start workflow after deployment.

Quick Start

Run the canary on a deployed URL to begin automated post-deploy monitoring and baseline comparison.

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 console errors after a deployment?

You can monitor a production URL for console errors after deployment by running a browser daemon to capture page failures, performance regressions, and baseline comparisons for automated alerts.

What is post-deploy canary monitoring and how does it detect production issues?

Post-deploy canary monitoring detects production issues by continuously watching a live app for console errors, performance regressions, and page failures to ensure quick detection and safe rollbacks.

Do I need baseline captures to perform canary monitoring on my web pages?

Yes, you need baseline captures to perform canary monitoring, as the Skill compares current browser daemon results against the pre-deploy state to detect anomalies across your configured page scope.

Can I configure the duration and page scope for ongoing production health monitoring?

Yes, you can configure the duration and page scope for ongoing production health monitoring to compare current results against baselines across multiple pages after a release.

What's the best way to catch performance regressions before users notice them after a release?

The best way to catch performance regressions after a release is to run automated post-deploy canary monitoring that alerts you when anomalies are detected against pre-deploy baselines.