canary

Detect post-deploy console errors, performance regressions, and page failures via the browse daemon.

1|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/nuurpro/Converza_ai --skill canary-nuurpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/nuurpro/Converza_ai/tree/main/.claude/skills/canary
Command: npx skills add https://github.com/nuurpro/Converza_ai --skill canary-nuurpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canary post-deploy monitoring finds console errors, performance regressions, and page failures in the live app, and compares against baselines so issues are caught before users notice.

Core Features & Use Cases

  • 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 after deploy to verify release health, or before deploy to capture a baseline for future comparisons.

Quick Start

Start monitoring a URL for a set duration with optional page lists and baseline capture before deploying.

Frequently Asked Questions about canary

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

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

Post-deploy monitoring detects console errors, performance regressions, and page failures by watching the live app. It compares periodic screenshots against pre-deploy baselines to catch issues before users notice them.

Can I capture a baseline before deploying to compare against later?

Yes, you can use this monitoring process before deploying to capture a pre-deploy baseline. This baseline data is then compared against the live app after release to identify anomalies and trigger alerts.

How do I verify release health after a production deploy?

Post-deploy verification checks release health by watching the live app for a set duration. It monitors specified page lists for console errors and performance regressions, outputting alerts and reports if failures occur.

What do I need to run post-deploy health checks on my app?

Post-deploy health checks require a running browse daemon, baseline data for comparison, and the target URL input. These inputs enable the monitoring process to generate alerts and artifacts like screenshots.

What artifacts and alerts are generated when detecting production regressions?

Detecting production regressions outputs alerts and artifacts such as screenshots and reports. These monitoring artifacts document the performance regressions and page failures found during the post-deploy verification period.

Does post-deploy monitoring work with specific page lists and durations?

Yes, post-deploy monitoring supports configurable durations and page lists. You specify which URLs to watch and for how long, allowing the browse daemon to detect console errors and page failures across targeted routes.