RevampKeyRevampKey home
Download

Check release health in Sentry with AI

After a deploy, compares the new release with the last one in Sentry: new issues, regressions, error volume, users affected and slower transactions. It ends with a clear verdict: healthy, watch, or roll back.

Read-onlyUses 5 Sentry toolsWorks in RevampKey, Claude Code, Codex and Cursor

Use in RevampKey

Get RevampKey to connect Sentry

RevampKey is a free desktop app for Mac, Windows and Linux. Install it, sign in, and Sentry is one click away with its skills already attached.

Download RevampKey

Not now? Use the skills in your current tool

curl -fsSL --create-dirs -o .claude/skills/sentry-release-health/SKILL.md https://revampkey.com/marketplace/sentry/skills/release-health/SKILL.md
Other agents
Other agents

When to use it

  • Right after a deploy
  • Deciding whether to roll back
  • Weekly release quality reviews

What it looks like

You

Is release 4.12.0 safe?

find_releasesfind_issuesfind_errorsfind_transactions+1 more
Agent

Watch, close to roll back. 4.12.0 has 3 new issues; one (CartSummary TypeError) hits 318 users in checkout. Errors per user are up 2.1x against 4.11.3 over the first 6 hours. Checkout p95 is unchanged. If the coupon fix cannot ship today, roll back.

The SKILL.md file

View raw
name: sentry-release-health

Check a release in Sentry after deploy for new issues, regressions, error spikes and slower transactions, and compare it with the previous release to decide whether it is safe or needs a rollback. Use when the user asks how a release or deploy is doing, whether it broke anything, or whether to roll back.

Read-only.

Steps

  1. Find the release with find_releases, defaulting to the latest in production, and the release before it.
  2. New problems: find_issues with firstSeen inside the release window and release:<version>. Separate brand-new issues from regressions, which are resolved issues that came back.
  3. Volume: find_errors for the error count and users affected in this release against the previous one over the same length of time after deploy.
  4. Performance: find_transactions for the slowest or most-changed endpoints and pages, with p75 or p95 duration before and after.
  5. Open the top two or three new issues with get_issue_details to judge their severity: a crash in checkout outweighs a noisy console warning.

Verdict

  • Healthy, watch or roll back, with the one or two facts that decide it.
  • New issues and regressions, by users affected.
  • Performance changes over about 20%.
  • Anything you could not measure because there was too little traffic yet.

Sentry tools it uses

  • find_releases
  • find_issues
  • find_errors
  • find_transactions
  • get_issue_details

Tool list from Sentry MCP documentation.

FAQ

Does it need release tracking set up?

Yes. Sentry must receive release versions from your deploys. Without them it can only compare time windows.

Can it roll back for me?

No. It gives the verdict; rolling back happens in your deploy tool.