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.

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

canary-watch