mcpField
R
release-health-dashboard-review

release-health-dashboard-review

github.com/sylphxaiCloud & DevOps147 installsUpdated today
Repository

About release-health-dashboard-review

A skill for product and release operations teams that turns release-health review into a dashboard specification and gated rollout decision artifact. It emphasizes segmented user signals, explicit rollback ownership, and post-release learning.

Key features

  1. 01Release context and rollout review
  2. 02Leading and lagging health signals
  3. 03Preflight and rollout gates
  4. 04Dashboard and alert specification
  5. 05Rollback ownership and recovery checks

Use cases

  1. 01Planning canary or staged releases
  2. 02Setting thresholds for release expansion or hold
  3. 03Preparing rollback triggers and owners

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill release-health-dashboard-review

After installing, type/release-health-dashboard-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/release-health-patterns.md

Details

From the project README

Release Health Dashboard Review

Use this skill to turn a recurring product-operations problem into a concrete, reviewable artifact instead of generic advice.

Workflow

  1. Identify release type, audience, platform/channel, rollout mechanism, critical user journeys, and rollback capability.
  2. Read references/release-health-patterns.md.
  3. Define leading and lagging health signals across reliability, conversion, payments, support, reviews, and adoption.
  4. Set gates for preflight, canary/staged rollout, expansion, hold, rollback, and post-release learning.
  5. Produce dashboard spec, alert thresholds, owner rotation, and release decision table.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not rely on green deploy/build status as user health proof.
  • Do not average away platform, version, region, plan, or device-specific regressions.
  • Every rollback trigger needs an owner, communication path, and recovery check.
  • Use store review and auto-update constraints when release rollback is not instant.

Output format

Release context:
Platform / rollout / rollback capability:

Dashboard spec:
| Signal | Baseline | Threshold | Segment | Owner | Action |
| --- | --- | --- | --- | --- | --- |

Gate decision table:
- <gate> -> <ship/hold/expand/rollback condition>

Post-release review:
- <learning, follow-up, docs/support update>

Comments

Markdown supported