canary

Monitor live applications for post-deployment console errors and performance regressions.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/miko06/MedicineSimulator --skill canary-miko06
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/miko06/MedicineSimulator/tree/main/.opencode/skills/gstack-canary
Command: npx skills add https://github.com/miko06/MedicineSimulator --skill canary-miko06

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Glob, AskUserQuestion, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill monitors live apps for console errors, performance regressions, and page failures post-deployment, taking periodic screenshots and comparing them against pre-deploy baselines to alert on anomalies.

Core Features & Use Cases

  • Post-Deploy Monitoring: Continuously monitors the live app for errors and performance issues.
  • Screenshot Comparison: Takes periodic screenshots and compares them against pre-deploy baselines.
  • Alerting: Alerts on detected anomalies, such as errors or performance regressions.
  • Use Case: Use this Skill to ensure the stability and performance of your application after deployment.

Quick Start

Run the canary skill to monitor the application for post-deploy issues.

Frequently Asked Questions about canary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor my application for post-deploy issues?

Post-deploy monitoring is achieved by continuously checking the live application for console errors, performance regressions, and page failures, alerting you when detected anomalies exceed your pre-deploy baselines.

What is a canary release and how does it detect performance regressions?

Canary release monitoring detects performance regressions by taking periodic screenshots of the live application and comparing them against pre-deploy baselines, alerting you when visual or functional anomalies are found.

What's the best way to automate error detection after a new deployment?

Automating error detection after deployment involves continuously monitoring the live app for console errors and page failures, comparing current state against pre-deploy baselines to alert on detected anomalies.

Do I need Bash to monitor live applications for post-deploy anomalies?

Yes, monitoring live applications for post-deploy anomalies requires Bash, along with Read, Write, Glob, and AskUserQuestion tools, to execute monitoring scripts and capture baseline comparisons.

Can I use screenshot comparison to verify application stability after release?

Yes, you can verify application stability after release by taking periodic screenshots of the live app and comparing them against pre-deploy baselines to detect visual anomalies, errors, and performance regressions.

Why does my canary monitoring alert on anomalies not present in the pre-deploy baseline?

Canary monitoring alerts on anomalies not present in the pre-deploy baseline because it continuously checks for new console errors, performance regressions, and page failures that emerged after the deployment went live.