canary

Monitor live URLs with the browse daemon and visual baselines to detect post-deploy failures.

1|Updated Mar 1, 2026

Search Tags:#performance #monitoring #alerts #baseline #canary #console-errors #post-deploy

Ready to run

npx skills add https://github.com/anishs1207/agentic-cli --skill canary-anishs1207

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/anishs1207/agentic-cli/tree/main/.agents/skills/gstack-canary
Command: npx skills add https://github.com/anishs1207/agentic-cli --skill canary-anishs1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring. Watches the live app for console errors, performance regressions, and page failures using the browse daemon. Takes periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies. Use when: "monitor deploy", "canary", "post-deploy check", "watch production", "verify deploy".

Core Features & Use Cases

Canary monitors live production for errors and performance issues.
Baseline comparisons and anomaly alerts help catch regressions early.
Works with the browse daemon to capture screenshots and synthesize actionable signals.

Quick Start

Run /canary <url> to start a 10-minute post-deploy monitoring session of the live site.

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 site for post-deploy regressions?▼

Post-deploy monitoring watches a live URL using the browse daemon to capture periodic screenshots and compare them against pre-deploy baselines, alerting on console errors, slow pages, and flaky behavior.

What is a canary check after deployment?▼

A canary check verifies a production deployment by monitoring the live application for anomalies over a defined window, comparing current state against baseline captures to catch regressions before users notice.

Do I need a baseline capture to start post-deploy monitoring?▼

Yes, baseline captures are required. The canary monitoring process compares live screenshots and performance metrics against these pre-deploy visual baselines to detect anomalies.

How do I detect console errors after a production release?▼

Detecting post-deploy console errors involves running a monitoring session on the live URL. The browse daemon watches the page and alerts on console errors and page failures during the monitoring window.

What's the best way to catch performance regressions in production?▼

Monitoring performance regressions requires comparing live application state against pre-deploy baselines. The browse daemon takes periodic screenshots and synthesizes actionable signals to alert on slow pages and anomalies.

How long does a post-deploy canary monitoring session last?▼

A standard post-deploy canary monitoring session runs for 10 minutes, watching the live site for console errors, performance issues, and page failures against pre-deploy baselines.