canary-watch
Continuously monitor Web application health after deployment, automatically detecting performance anomalies, error rates, and functional degradation, supporting alert notifications and root cause analysis.
npx skills add affaan-m/everything-claude-code --skill canary-watchBefore / After Comparison
1 组After deployment, it's necessary to manually refresh pages to check functionality, view logs to troubleshoot errors, and use monitoring tools to observe performance metrics. Problems are often discovered only after they have already affected users. Root cause analysis typically takes 1-2 hours, making quick rollback difficult.
After deployment, monitoring patrols are automatically initiated, regularly visiting key pages and detecting error rates and response times. In case of anomalies, alerts are immediately triggered, providing detailed log and metric analysis. Problems are located within 5 minutes, supporting automatic rollback decisions.
canary-watch
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
1. HTTP Status — is the page returning 200?
2. Console Errors — new errors that weren't there before?
3. Network Failures — failed API calls, 5xx responses?
4. Performance — LCP/CLS/INP regression vs baseline?
5. Content — did key elements disappear? (h1, nav, footer, CTA)
6. API Health — are critical endpoints responding within SLA?
Watch Modes
Quick check (default): single pass, report results
/canary-watch https://myapp.com
Sustained watch: check every N minutes for M hours
/canary-watch https://myapp.com --interval 5m --duration 2h
Diff mode: compare staging vs production
/canary-watch --compare https://staging.myapp.com https://myapp.com
Alert Thresholds
critical: # immediate alert
- HTTP status != 200
- Console error count > 5 (new errors only)
- LCP > 4s
- API endpoint returns 5xx
warning: # flag in report
- LCP increased > 500ms from baseline
- CLS > 0.1
- New console warnings
- Response time > 2x baseline
info: # log only
- Minor performance variance
- New network requests (third-party scripts added?)
Notifications
When a critical threshold is crossed:
-
Desktop notification (macOS/Linux)
-
Optional: Slack/Discord webhook
-
Log to
~/.claude/canary-watch.log
Output
## Canary Report — myapp.com — 2026-03-23 03:15 PST
### Status: HEALTHY ✓
| Check | Result | Baseline | Delta |
|-------|--------|----------|-------|
| HTTP | 200 ✓ | 200 | — |
| Console errors | 0 ✓ | 0 | — |
| LCP | 1.8s ✓ | 1.6s | +200ms |
| CLS | 0.01 ✓ | 0.01 | — |
| API /health | 145ms ✓ | 120ms | +25ms |
### No regressions detected. Deploy is clean.
Integration
Pair with:
-
/browser-qafor pre-deploy verification -
Hooks: add as a PostToolUse hook on
git pushto auto-check after deploys -
CI: run in GitHub Actions after deploy step
Weekly Installs494Repositoryaffaan-m/everyt…ude-codeGitHub Stars144.9KFirst Seen10 days agoSecurity AuditsGen Agent Trust HubPassSocketPassSnykWarnInstalled oncodex459opencode437cursor432github-copilot431antigravity431gemini-cli430
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill