AI agent skill · by @Devin-AXIS

Sentry Release Health

Assess release health from Sentry errors, regressions, affected users, crash evidence, and comparison with the previous stable release.

Testing Qa

Open in directory View original source ↗

Archived 2026-10-23 · Source updated 2026-09-16. Check the original repository for the latest version.

SKILL.md instructions

# Sentry Release Health

1. Resolve the release and production environment exactly.
2. Compare it with the previous relevant stable release over equivalent windows.
3. Report new and regressed issues, affected users, severity, and high-confidence change points.
4. Distinguish incomplete rollout, low traffic, and missing instrumentation from healthy behavior.
5. Recommend continue, monitor, pause, or rollback only when the evidence supports that choice.

Never claim a release is safe solely because no events were returned.

Related skills

Proof Video

by @openclaw

Add subtitles, captions, narration cues, or zoom to a proof video or PR recording using repo-local capture helpers and a system ffmpeg renderer.

Slack E2e

by @openclaw

Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

Telegram E2e Userbot

by @openclaw

Prove user-visible OpenClaw Telegram behavior on Telegram's Test Server with Convex-leased team credentials; drive real-user turns and record messages, edits, deletions, reactions, typing, or rich…

Module Regression

by @affaan-m

Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed…