canary-watch

Monitors deployed URLs for HTTP, console, performance, and API regressions after deploys.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill canary-watch-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary-watch
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/canary-watch
Command: npx skills add https://github.com/ibytechaos/claude --skill canary-watch-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After deploying to production, merging a risky PR, or upgrading dependencies, teams often lack immediate visibility into whether the release introduced regressions. This Skill continuously watches a deployed URL and alerts you the moment something breaks. ## Core Features & Use Cases - Multi-Signal Monitoring: Checks HTTP status, new console errors, network failures, Core Web Vitals (LCP/CLS/INP), key page content, and API endpoint health against baselines. - Flexible Watch Modes: Run a single quick check, a sustained watch at a set interval for a defined duration, or a diff comparison between staging and production. - Tiered Alerting: Classifies findings as critical, warning, or info, with desktop notifications, optional Slack/Discord webhooks, and a persistent log file. - Use Case: After pushing a release, run a sustained watch on your production URL every 5 minutes for 2 hours to catch regressions during the launch window before users report them. ## Quick Start Ask the AI to run canary-watch against your deployed URL, for example to monitor https://myapp.com every 5 minutes for 2 hours and report any regressions.

Frequently Asked Questions about canary-watch

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

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

Run canary-watch against your deployed URL to check HTTP status, console errors, network failures, performance metrics, and key page content. Use quick check mode for a single pass or sustained watch mode to poll at intervals over a set duration.

How to compare staging vs production environments automatically?

Use the diff mode with the --compare flag followed by your staging and production URLs. The skill runs checks against both environments and reports differences in status, errors, and performance metrics.

What performance metrics does post-deploy monitoring check?

It tracks Core Web Vitals including LCP, CLS, and INP against recorded baselines. Critical alerts fire when LCP exceeds 4 seconds, while warnings trigger on LCP increases over 500ms or CLS above 0.1.

Can I get Slack notifications when a deploy breaks production?

Yes, critical threshold violations trigger desktop notifications on macOS and Linux, plus optional Slack or Discord webhooks. All events are also logged to ~/.claude/canary-watch.log for later review.

When should I use canary monitoring versus pre-deploy testing?

Use pre-deploy verification like browser-qa before release, and canary-watch after deployment to catch issues that only appear in production. It pairs well as a PostToolUse hook on git push or as a CI step after the deploy stage.