Agent skill · software engineering · jeremylongshore
sentry-release-management
Manage Sentry releases with versioning, commit association, and source
Why this skill is useful
Adds specific commands and workflows for managing Sentry releases that the AI wouldn't reliably generate on its own.
What it needs
Requires sentry-cli installed locally. Requires sentry account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Release Management Overview Manage the full Sentry release lifecycle: create versioned releases, associate commits for suspect commit detection, upload source maps for readable stack traces, and monitor release health with crash-free rates and adoption metrics. Every production deploy should create a Sentry release so errors are grouped by version and regressions are caught immediately. Prerequisites Sentry CLI installed: npm install -g @sentry/cli (v2.x) or use npx @sentry/cli Auth token with project:releases and org:read scopes from sentry.io/settings/auth-tokens/ Environment variables set: SENTRYAUTHTOKEN, SENTRYORG, SENTRYPROJECT Source maps generated by your build (e.g., tsc --sourceMap, Vite build.sourcemap: true) GitHub/GitLab integration installed in Sentry for automatic commit association (Settings > Integrations) Instructions Step 1 — Create a Release and Associate Commits Choose a release naming convention. Sentry accepts any string, but two patterns dominate production usage: Semver naming ties releases to your package version: Commit SHA naming ties releases to exact deployments: After creating the release, associate commits. This is what powers suspect commits — Sentry's ability to identify which commit likely caused a new issue by matching error stack frames to recently changed files: When --auto runs, Sentry walks the git log from the previous release's last commit to the current HEAD. It stores each commit's author, changed files, and message. When a new error arrives, Sentry matches the stack trace file paths against recently changed files and suggests the author as the likely owner. Step 2 — Upload Source Maps and Release Artifacts Source maps let Sentry translate minified stack traces into original source code. Upload them before deploying — Sentry does not retroactively apply source maps to existing events. The --url-prefix must match how your JS files are served. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-release-management--133e91