canary

Monitors deployed web apps for console errors, performance regressions, and page failures using browser screenshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploys that pass CI can still break in production due to missing environment variables, stale CDN caches, or slow migrations. This Skill watches the live app after a deploy and catches regressions in the first minutes instead of hours. ## Core Features & Use Cases - Baseline Capture: Takes pre-deploy screenshots, console error counts, and load times per page, saved to a baseline manifest for later comparison. - Continuous Monitoring Loop: Checks each monitored page every 60 seconds for a configurable duration (1-30 minutes), comparing results against the baseline and alerting only on persistent changes across 2+ consecutive checks. - Severity-Based Alerts: Classifies findings as CRITICAL (page load failure), HIGH (new console errors), MEDIUM (2x load time regression), or LOW (new broken links), each with screenshot evidence. - Use Case: After deploying a new release, run the canary against your production URL for 10 minutes to verify the homepage, dashboard, and settings pages still load cleanly with no new console errors. ## Quick Start Ask the assistant to run /canary https://your-app.com to monitor the deployed site for 10 minutes and report any regressions against the baseline.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor a website after deployment for errors?

Run /canary with your production URL to watch the site for 10 minutes. It checks each page every 60 seconds for new console errors, load failures, and performance regressions, alerting only when issues persist across consecutive checks.

How to capture baseline screenshots before deploying?

Run /canary <url> --baseline before deploying. It saves screenshots, console error counts, and load times per page to .gstack/canary-reports/baseline.json, which later monitoring runs compare against.

Can I customize which pages and duration the canary monitors?

Yes. Use --pages to specify paths like /,/dashboard,/settings and --duration to set monitoring from 1 to 30 minutes. Without --pages, it auto-discovers the top navigation links and asks you to confirm.

What counts as a performance regression in canary monitoring?

A page load time exceeding 2x the baseline is flagged as a MEDIUM alert. Thresholds are relative to your own baseline, not absolute industry numbers, and alerts require persistence across 2 or more consecutive checks.

Does the canary skill modify code or roll back deploys automatically?

No. It is read-only: it observes, screenshots, and reports. When a critical alert fires, it asks whether you want to investigate, continue monitoring, roll back, or dismiss, but never changes code on its own.