canary-watch

Monitor deployed URLs to detect HTTP, performance, and content regressions.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/GGEdu/claude-god-mode-template --skill canary-watch-ggedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary-watch
Source: https://github.com/GGEdu/claude-god-mode-template/tree/main/skills/canary-watch
Command: npx skills add https://github.com/GGEdu/claude-god-mode-template --skill canary-watch-ggedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects post-deploy regressions by continuously monitoring a deployed URL for errors, performance shifts, and missing content, enabling rapid remediation.

Core Features & Use Cases

  • Post-deploy health checks: keep production and staging URLs under watch after releases or dependency updates.
  • Multi-metric monitoring: track HTTP status, performance (LCP/CLS/INP), and content availability to surface regressions early.
  • Flexible watch modes: run a quick one-off check, sustained monitoring, or cross-environment comparison to validate fixes.
  • Alerts and reporting: generate clear reports and trigger notifications when thresholds are breached.

Quick Start

Run the canary-watch command against your deployment URL to begin continuous monitoring.

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

To monitor a deployed URL for regressions, you can run continuous health checks against your staging or production endpoint to track HTTP status, performance metrics, and content availability after deploys.

What is post-deploy health monitoring and how does it detect regressions?

Post-deploy health monitoring continuously checks a deployed URL for HTTP errors, performance shifts like LCP and CLS, and missing content, enabling rapid detection of regressions after merges or dependency upgrades.

Can I check staging and production URLs at the same time to validate fixes?

Yes, you can use cross-environment comparison watch modes to monitor staging and production URLs simultaneously, allowing you to validate fixes and detect HTTP issues across different deployment environments.

How do I set up alerts for HTTP status changes and performance regressions?

You can configure watch modes with specific thresholds to trigger alerts and generate reports when HTTP status changes, performance regressions, or missing content are detected on your monitored URLs.

Does post-deploy URL monitoring work for one-off checks or does it require sustained monitoring?

Post-deploy URL monitoring supports flexible watch modes, allowing you to run a quick one-off check to validate a deployment or sustained continuous monitoring to catch delayed regressions.

What are the limitations of post-deploy URL health monitoring?

This monitoring requires a reachable HTTP or HTTP(S) target URL and is limited to detecting HTTP issues, performance metrics like LCP and CLS, and missing content, rather than functional backend logic errors.