Monitor live URLs for console errors, performance regressions, and page failures.
npx skills add https://github.com/yolopunk/jedi --skill canary-yolopunk
Please help me install this Agent Skill. Skill: canary Source: https://github.com/yolopunk/jedi/tree/main/.claude/skills/gstack/canary Command: npx skills add https://github.com/yolopunk/jedi --skill canary-yolopunk
Post-deploy canary monitoring. Watches the live app for console errors, performance regressions, and page failures using the browse daemon. Takes periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies. Use when: "monitor deploy", "canary", "post-deploy check", "watch production", "verify deploy".
Baseline capture and page discovery prior to deployment to establish reference metrics. Continuous post-deploy monitoring with periodic checks, screenshot capture, console and performance analysis. Alerting and guidance for remediation when anomalies are detected, plus an audit trail of sessions.
Invoke the canary with a URL and optional arguments to start a 10-minute monitor, then review the reports in .gstack/canary-reports.
High-intent search queries and answers about installing and using this skill.
Monitor a production URL for post-deploy issues by capturing periodic screenshots, checking for console errors, and comparing live performance against pre-deploy baselines to alert on anomalies.
A canary check is a post-deploy monitoring process that watches a live app for console errors, performance regressions, and page failures by comparing current behavior against pre-deploy baselines.
Capture baseline metrics and discover pages prior to deployment to establish reference data, enabling continuous post-deploy monitoring to compare live results against these saved artifacts.
Yes, post-deploy checks require the browse daemon and gstack tooling to capture screenshots, analyze console and performance data, and output canary reports under .gstack/canary-reports.
Get alerts for performance regressions by running continuous post-deploy monitoring with periodic checks that compare live application behavior against captured baselines and flag anomalies.
Monitoring production pages for console errors requires configurable duration settings and depends on the browse daemon, limiting checks to pages accessible via the provided URL and gstack environment.
Ronin15Compare SDL3 HammerEngine metrics against baselines to flag performance regressions.
OmerFarukOrucMonitor production deployments with a browse daemon capturing screenshots, console errors, and performance metrics.
devs6186Monitors live apps for console errors, page failures, performance regressions, and screenshot anomalies after deployment.
zhu637882-stackMonitor live apps for console errors, performance regressions, and page failures.
