canary-watch

Monitor deployed URLs for regressions and health issues after deployments.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/zardusai-cyber/zardus_setup --skill canary-watch-zardusai-cyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary-watch
Source: https://github.com/zardusai-cyber/zardus_setup/tree/main/ecc/skills/canary-watch
Command: npx skills add https://github.com/zardusai-cyber/zardus_setup --skill canary-watch-zardusai-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitors a deployed URL to detect regressions and health issues after deployments.

Core Features & Use Cases

  • Configurable watch modes: quick check, sustained watch, and diff mode to compare environments.
  • Multi-faceted health checks: HTTP status, console errors, network failures, performance (LCP/CLS/INP), and API health.
  • Notifications and escalation: alerts to desktop notifications and optional webhooks (Slack/Discord) when thresholds are crossed.

Quick Start

Run canary-watch https://your-app.example.com to begin post-deploy monitoring immediately.

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 URL for regressions after a deployment?

Post-deploy monitoring tracks a deployed URL to detect regressions and health issues after deployments. It applies to post-deploy verification, PR merges, and dependency upgrades across production and staging environments.

What health checks should I run after a production deployment?

Post-deploy health checks should monitor HTTP status, console errors, network failures, and performance metrics (LCP, CLS, INP), plus API health. These checks detect regressions and health issues after deployments across production and staging.

Can I compare staging and production environments after a merge?

Diff mode compares environments after PR merges or dependency upgrades. This configurable watch mode detects regressions by contrasting a deployed staging URL against production environments.

How do I set up threshold-based alerts for post-deploy monitoring?

Threshold-based alerts trigger desktop notifications and optional webhooks to Slack or Discord when crossed. Configurable watch modes sustain monitoring after deploys to escalate regressions and health issues across environments.

Does canary-watch support Slack or Discord notifications for uptime alerts?

Canary-watch supports alerts to desktop notifications and optional webhooks for Slack or Discord. It sends these alerts when threshold-based monitoring detects regressions or health issues during sustained post-deploy watches.