canary

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

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

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 as a baseline manifest for later comparison. - Continuous Monitoring Loop: Checks each monitored page every 60 seconds for a configurable duration, 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. - Health Report: Produces a per-page summary report with status, error counts, and average load times, saved as Markdown and JSON. - 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 correctly with no new console errors. ## Quick Start Ask the AI to run the canary monitor against your production URL for 10 minutes after a deploy and alert you if any page regresses compared to 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 the canary skill with your production URL to monitor pages every 60 seconds for a set duration. It captures screenshots, checks console errors, and measures load times, alerting you when results deviate from the pre-deploy baseline.

How to detect performance regressions after a deploy?

Capture a baseline before deploying with the --baseline flag, then run monitoring after the deploy. The canary flags any page whose load time exceeds 2x the baseline as a MEDIUM severity regression.

Can I monitor specific pages instead of the whole site?

Yes, pass a comma-separated page list with the --pages flag, such as /,/dashboard,/settings. Without it, the canary auto-discovers the top navigation links and asks you to confirm which pages to monitor.

Why does the canary not alert on a single failed check?

The canary only alerts on patterns persisting across 2 or more consecutive checks to avoid false positives from transient network blips. It compares against baselines rather than absolute thresholds, so pre-existing errors do not trigger alerts.

What is the difference between baseline mode and quick mode?

Baseline mode (--baseline) captures pre-deploy screenshots and metrics, then stops so you can deploy. Quick mode (--quick) runs a single-pass health check with no continuous monitoring, useful for a fast production sanity check.