canary

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

1|Updated Dec 23, 2025

Search Tags:#monitoring #screenshots #production #alerts #baseline #health #canary

Ready to run

npx skills add https://github.com/rkumar261/studio-cast --skill canary-rkumar261

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/rkumar261/studio-cast/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/rkumar261/studio-cast --skill canary-rkumar261

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy reliability is fragile: small issues like missing environment variables, slow migrations, or unexpected page failures can slip into production. This skill provides a safety net by watching the live app with a browse daemon, taking screenshots, collecting console errors and performance data, and alerting on anomalies.

Core Features & Use Cases

Continuous post-deploy monitoring with configurable duration and pages to cover critical user flows.
Baseline capture and regression checks for console errors, load times, and visual snapshots to detect drift.
Health reporting with evidence (screenshots and metrics) to accelerate triage and rollback decisions.

Quick Start

Monitor a production URL for 10 minutes by invoking the canary skill; adjust duration or pages as needed.

Frequently Asked Questions about canary

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

FAQPage Schema

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

Post-deploy canary monitoring uses a browse daemon to continuously check a live production URL, capturing console errors, performance metrics, and visual snapshots to detect anomalies after deployment.

How do I monitor a production URL for console errors after a deployment?▼

Invoke the canary monitoring skill to run a browse daemon against your production URL for a set duration. It captures baseline metrics and alerts on console errors, page failures, and performance regressions.

Can I configure specific pages and duration for continuous production health checks?▼

Yes, production health checks are configurable by duration and pages. You can monitor critical user flows continuously for a default of 10 minutes and adjust both parameters as needed for your coverage.

How does baseline capture work for detecting performance regressions in production?▼

Baseline capture records initial console logs, load times, and visual snapshots from your production URL. The monitoring daemon then compares subsequent checks against this baseline to alert on any detected drift or regressions.

Where are health reports and monitoring screenshots stored for audit and rollback workflows?▼

Health reports, baseline captures, per-page monitoring results, and screenshots are stored in the .gstack directory. This provides evidence for audit trails and accelerates rollback decisions after a deployment.

What's the best way to automate post-deploy monitoring for critical user flows?▼

Automate post-deploy monitoring by invoking the canary skill against a production URL. It runs a browse daemon to capture baselines, check critical pages, and alert on anomalies without requiring additional dependencies.