SKILL

canary-watch

Use this skill to monitor and verify a deployed URL after releases — checks HTTP endpoints, SSE streams, static assets, console errors, and performance regressions after deploys, merges, or dependency upgrades. Smoke / canary / post-deploy verification.

Target: Target not categorized. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original English text

Topics in the source

  • Canary Watch — Post-Deploy Monitoring
  • When to Use
  • How It Works
  • What It Watches
  • Watch Modes
  • Alert Thresholds
  • Notifications
  • Output

After deploying to production or staging After merging a risky PR When you want to verify a fix actually fixed it Continuous monitoring during a launch window After dependency upgrades Monitors a deployed URL for regressions. Runs in a loop until stopped or until the watch window expires. Quick check (default): single pass, report results Sustained watch: check every N minutes for M hours Diff mode: compare staging vs production When a critical threshold is crossed: Desktop notification (macOS/Linux) Optional: Slack/Discord webhook Log to /.claude/canary-watch.log Pair with: /browser-qa for pre-deploy verification Hooks: add as a PostToolUse hook on git push to auto-check after deploys CI: run in GitHub Actions after deploy step

Source repository
affaan-m/ECC
Source file
skills/canary-watch/SKILL.md
Fixed revision
d2ef2680594f9a17526a6e1a2e18b3d242c5d17b
Read the complete original documentation ↗

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: affaan-m/ECC · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T15:01:43.459Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.