Monitor production pages for console errors, performance regressions, and page failures.
npx skills add https://github.com/westn/gstack-pi-port --skill canary-westn
Please help me install this Agent Skill. Skill: canary Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack/canary Command: npx skills add https://github.com/westn/gstack-pi-port --skill canary-westn
This capability enables post-deploy reliability by continuously watching the live app for console errors, performance regressions, and page failures. It helps catch issues that slip through CI before users notice.
Run the canary after deployment with /skill:canary <url> to monitor production for 10 minutes.
High-intent search queries and answers about installing and using this skill.
Post-deploy reliability monitoring uses a browse daemon to continuously check production pages for console errors, performance regressions, and page failures. It captures a baseline and compares it against live traffic to detect regressions after a new release.
To catch console errors and performance regressions after a release, run an automated canary monitoring check against your production URL. It performs continuous health checks across multiple pages for 10 minutes to identify critical, high, or medium issues.
Baseline capture for production monitoring is handled automatically by the browse daemon. It records initial page health and performance metrics, then compares subsequent checks against this baseline to identify regressions and page failures.
No external dependencies are required to run automated alerts for post-deploy verification. The monitoring capability coordinates baseline capture, page checks, and alerts with built-in guardrails for critical, high, and medium issues.
Yes, canary monitoring verifies continuous health across multiple production pages. Using a browse daemon, it runs a 10-minute monitoring cycle to detect page failures and performance regressions, providing actionable alert guidance.
Post-deploy monitoring catches issues missed by CI by continuously watching the live app. If issues are not detected, ensure the browse daemon is running against the correct production URL and that baseline capture completed successfully before comparison.
TobiasPerryMonitor live production URLs for console errors and performance regressions.
algorithmbasicsMonitor production apps for console errors, performance regressions, and page failures.
ectoReview React/TypeScript console code for WebSocket protocol and performance issues.
UlanxxMonitor live URLs for console errors, performance regressions, and page failures.
