Monitor a production URL for anomalies during the first 10 minutes post-deploy.
npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill canary-akiyoshi
Please help me install this Agent Skill. Skill: canary Source: https://github.com/akiyoshi/gstack-copilot-jp/tree/main/.github/skills/canary Command: npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill canary-akiyoshi
Post-deploy monitoring is essential to catch issues that pass CI but fail in production, such as missing environment variables, cache issues, or slow migrations. This skill provides an automated, time-bounded post-deploy health check to detect regressions early and keep services reliable.
Run /canary <url> to start a 10-minute canary monitor on the target production URL.
High-intent search queries and answers about installing and using this skill.
Post-deploy canary checks are automated by actively monitoring a production URL for anomalies during the first 10 minutes after deployment to detect errors and performance regressions. The monitor observes live behavior to identify issues that passed CI checks.
A post-deploy monitoring baseline captures normal service behavior before or during deployment to detect drift. By comparing live production metrics against this baseline, the monitoring process identifies performance regressions and emerging errors immediately after the release.
To run a 10-minute canary monitor, execute the monitoring command with your target production URL. The automated health check then observes the live web service continuously for the defined window to verify no critical issues appear.
Yes, post-deploy monitoring is specifically designed to catch issues that pass CI but fail in production. It actively observes live URLs to detect missing environment variables, cache issues, slow migrations, and other runtime anomalies that automated tests miss.
Production observability checks produce structured health alerts categorized as CRITICAL, HIGH, and MEDIUM. These alerts include remediation evidence such as logs, timings, and screenshots to guide quick resolution of detected post-deploy anomalies.
Yes, post-deploy reliability checks feature configurable monitoring durations, with a default 10-minute window for immediate observation. This time-bounded approach ensures active monitoring captures early anomalies without indefinite resource consumption.
Ronin15Compare SDL3 HammerEngine metrics against baselines to flag performance regressions.
nahisahoConfigure production monitoring, alerting, and incident response runbooks.
westnMonitor production pages for console errors, performance regressions, and page failures.
TimHL5Monitor post-deploy web apps for console errors, performance metrics, and page failures.
