Monitor production deployments for console errors, performance regressions, and visual anomalies.
npx skills add https://github.com/a29paul/hexlens --skill canary-a29paul
Please help me install this Agent Skill. Skill: canary Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/canary Command: npx skills add https://github.com/a29paul/hexlens --skill canary-a29paul
Deploying code to production carries inherent risk. This skill automates post-deploy verification by continuously monitoring the live application for console errors, performance regressions, and visual anomalies, providing immediate feedback when a release introduces issues.
Use the canary skill to monitor your latest production deployment for console errors, performance regressions, and visual anomalies.
High-intent search queries and answers about installing and using this skill.
Post-deploy canary monitoring automates live application inspection using a browse daemon to detect console errors, performance regressions, and visual anomalies after code releases. It captures periodic screenshots and compares them against pre-deploy baselines to catch visual bugs.
Post-deploy canary verification is an automated process that watches live applications for regressions following a production deployment. You need it to catch console errors, performance degradations, and visual bugs immediately after shipping code to prevent widespread user impact.
Visual regression detection takes periodic screenshots of the live application and compares them against pre-deploy baseline images. This automated comparison catches visual bugs introduced by the release so you can address them before they affect all users.
Yes, the browse daemon is required for page interaction and live application inspection during post-deploy monitoring. You also need baseline image storage for visual comparison and alerting mechanisms configured to receive anomaly notifications.
Yes, anomaly alerting triggers notifications when performance regressions or console errors are detected during post-deploy monitoring. This immediate feedback allows you to roll back or fix issues before they impact all users.
Automated screenshot comparison requires pre-deploy baseline images to function and is limited to detecting visual anomalies. It does not replace functional testing and must be paired with alerting mechanisms to ensure detected regressions trigger rollback workflows.
nuurproDetect post-deploy console errors, performance regressions, and page failures via the browse daemon.
bejranondaDetect JavaScript errors and collect browser diagnostics from web pages.
GTC6244Measure web performance and detect regressions against baselines in CI workflows.
GenEducationDetect post-deploy regressions by checking page health, console errors, performance, and visual changes.
