Monitor deployed URLs for console errors, performance regressions, and page failures.
npx skills add https://github.com/lachieh/babytalk --skill canary-lachieh
Please help me install this Agent Skill. Skill: canary Source: https://github.com/lachieh/babytalk/tree/main/.claude/skills/gstack/canary Command: npx skills add https://github.com/lachieh/babytalk --skill canary-lachieh
Post-deploy canary monitoring solves the issue of catching production issues that slip past CI, by watching the live app for errors, regressions, and failures, and by taking baselines and alerts early.
Invoke /canary with your deployment URL to start a 10-minute post-deploy health monitor and baseline checks.
High-intent search queries and answers about installing and using this skill.
A post-deploy canary monitors production stability by watching a deployed URL for console errors, performance regressions, and page failures using a browse daemon. It captures baselines and alerts on detected anomalies.
A post-deploy canary check is a monitoring technique that watches a live application URL for console errors and performance regressions using an automated browse daemon. It operates in three phases: baseline capture, discovery, and continuous monitoring to detect anomalies.
Yes, canary monitoring supports page-specific checks and configurable durations. Invoking the canary with your deployment URL initiates a 10-minute post-deploy health monitor, capturing baselines and taking automated screenshots of the specified pages.
You can detect performance regressions in production by capturing a health baseline before release, then continuously monitoring the live URL. The canary compares live telemetry against this baseline to identify and alert on performance anomalies.
Yes, post-deploy canary monitoring captures automated screenshots during its continuous monitoring phase. These screenshots provide visual evidence of page failures and console errors when anomalies are detected in the deployed production environment.
Canary checks using a browse daemon are limited to detecting client-side console errors, performance regressions, and page failures on the URL provided. This approach does not monitor backend server health, database latency, or internal API telemetry outside of visible page behavior.
Ronin15Compare SDL3 HammerEngine metrics against baselines to flag performance regressions.
makyua-sanMonitor production deployments for console errors, performance regressions, and page failures.
GTC6244Merge PRs, wait for CI, deploy to production, and run canary health checks.
tsenseiMonitor a live URL for console errors, performance changes, and page failures.
