Monitor deployed apps for console errors, performance regressions, and page failures.
npx skills add https://github.com/scanbott/claude-skills --skill canary-scanbott
Please help me install this Agent Skill. Skill: canary Source: https://github.com/scanbott/claude-skills/tree/main/gstack/canary Command: npx skills add https://github.com/scanbott/claude-skills --skill canary-scanbott
Post-deploy canary monitoring is essential to catch regressions before they affect users. This skill watches the live app for console errors, performance regressions, and page failures using the browse daemon. It also takes periodic screenshots, compares against pre-deploy baselines, and raises alerts when anomalies are detected.
Run the canary monitor after deployment to start watching production for anomalies.
High-intent search queries and answers about installing and using this skill.
Post-deploy canary monitoring detects production anomalies by comparing live baselines against pre-deploy states using the browse daemon to take periodic screenshots and trigger alerts on console errors, performance regressions, and page failures.
Canary-based health checking is a post-deploy monitoring technique that verifies production stability by continuously watching the live app for console errors, performance regressions, and page failures against pre-deploy baselines to catch regressions before they affect users.
Automated anomaly alerts for console errors and performance regressions are set up by running a post-deploy canary monitor that compares live application states against pre-deploy baselines and surfaces detected issues to engineers.
Yes, baseline-driven visual checks use periodic screenshots of the live application to provide quick verification of production stability and serve as visual rollback signals when anomalies are detected.
Baseline-driven visual checks are needed when you must verify production stability after deployments, providing quick visual verification and rollback signals by comparing live screenshots against pre-deploy baselines to catch regressions before user impact.
The best way to catch post-deploy regressions before they affect users is to run a canary monitor immediately after deployment, comparing live baselines against pre-deploy states to detect console errors, performance regressions, and page failures.
timurgaleevMonitor post-deploy web apps for defects and performance regressions.
binfen1Monitor live apps for console errors, performance regressions, and page failures.
SnakeODiagnose Angular runtime errors using DevTools, ng.probe, and console utilities.
chriswesttMonitor deployed apps for console errors, performance regressions, and page failures.
