canary

Monitor live web applications for post-deploy regressions via screenshots and console errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catch silent production failures that slip past CI by continuously watching live pages after a deploy, surfacing new console errors, performance regressions, page failures, and visual diffs with evidence.

Core Features & Use Cases

  • Continuous post-deploy monitoring: run a short, configurable canary window (default 10 minutes) to validate a release in production.
  • Baseline comparisons and screenshots: capture pre-deploy baselines or take quick pre-deploy snapshots, then compare periodic screenshots and metrics to detect regressions.
  • Evidence-driven alerts and workflow: alerts include screenshot paths and specifics; options to investigate, continue monitoring, rollback, or dismiss; saves JSON/markdown reports for auditing.
  • Use case: After merging and deploying a release, run the skill against the homepage and top navigation pages to detect new console errors or a 2x performance regression within the first 10 minutes.

Quick Start

Run /canary https://your-site.example to monitor production for 10 minutes and produce a canary report with screenshots and alerts.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor a live web application for post-deploy regressions?▼

Monitor a live web application for post-deploy regressions by taking periodic screenshots, checking console errors, and measuring performance against pre-deploy baselines to detect page failures and visual diffs.

What is the best way to catch silent production failures after a release?▼

Catch silent production failures by running a short post-release canary window to continuously watch live pages, surfacing new console errors, performance regressions, and page failures with screenshot evidence.

How do I detect performance regressions in production after deploying?▼

Detect performance regressions in production by comparing periodic screenshots and metrics against pre-deploy baseline snapshots during a configurable monitoring window of 1 to 30 minutes.

Do I need a local browse daemon to check for console errors after a deploy?▼

Yes, you need a local browse daemon for automated navigation and snapshot commands, along with baseline artifacts or pre-deploy snapshots and filesystem access to write reports and screenshots.

Can I generate audit reports for post-release page failures and visual diffs?▼

Yes, generate audit reports by saving JSON and markdown reports that include alert specifics and screenshot paths, providing options to investigate, continue monitoring, rollback, or dismiss.

When should I run a canary monitoring window for my web application?▼

Run a canary monitoring window for short post-release periods of 1 to 30 minutes across specified pages or discovered navigation links to detect new errors and performance regressions immediately after deploying.