Agent skill · operations · affaan-m
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.
Why this skill is useful
Adds specific monitoring commands and alert thresholds for post-deployment verification that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. About 2k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Canary Watch — Post-Deploy Monitoring When to Use 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 How It Works Monitors a deployed URL for regressions. Runs in a loop until stopped or until the watch window expires. What It Watches Watch Modes Quick check (default): single pass, report results Sustained watch: check every N minutes for M hours Diff mode: compare staging vs production Alert Thresholds Notifications When a critical threshold is crossed: Desktop notification (macOS/Linux) Optional: Slack/Discord webhook Log to ~/.claude/canary-watch.log Output Integration 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
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/canary-watch--9c5c30