Menu

Individual skill

release-health

0upvotes

Monitoring release health — crash-free rates, adoption, and catching bad deploys early — platform-agnostic patterns.

skills/release-health/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
53
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Every release is a hypothesis: "this version is better than the last."
Release health monitoring tests that hypothesis with data — crash-free
rates, error deltas, performance changes, and adoption — so bad releases
get caught in minutes, not days. This skill covers the release-health
discipline for web, mobile, and backend deploys.

## When to use

- Tracking whether a new release is healthy or regressing
- Setting up crash-free session/user metrics (especially mobile)
- Comparing error and performance across versions
- Building progressive rollout / canary analysis