Agent skill · software engineering · jeremylongshore
sentry-ci-integration
Integrate Sentry into CI/CD pipelines for automated release creation,
Why this skill is useful
Adds a complete set of executable scripts for automating Sentry release management in CI/CD pipelines, which the AI cannot generate from general knowledge alone.
What it needs
Requires npm installed locally. Requires sentry account access. About 8k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry CI Integration Overview Sentry releases connect errors to the code that caused them. Automating release creation in CI/CD ensures every deploy has commit association (suspect commits), source maps for readable stack traces, and deployment tracking across environments. This skill covers sentry-cli commands, the official GitHub Action, build tool plugins (@sentry/webpack-plugin, @sentry/vite-plugin, @sentry/esbuild-plugin), and multi-platform CI configurations. Prerequisites Sentry account with a project at sentry.io SENTRYAUTHTOKEN — generate at sentry.io/settings/auth-tokens/ with scopes project:releases and org:read SENTRYORG and SENTRYPROJECT environment variables matching your organization and project slugs Source maps generated during your build step (devtool: 'source-map' in webpack, build.sourcemap: true in Vite) Git integration installed in Sentry (sentry.io/settings/integrations/ — GitHub, GitLab, or Bitbucket) for commit association sentry-cli available via npm install -g @sentry/cli, npx @sentry/cli, or the getsentry/sentry-cli Docker image Instructions Step 1 — Configure Environment Variables and Auth Token Set up the three required environment variables in your CI platform. Every sentry-cli command reads these automatically. For build tool plugins (@sentry/webpack-plugin, @sentry/vite-plugin, @sentry/esbuild-plugin), the same three environment variables are read automatically. No additional configuration needed. Verify your token works locally before committing CI configuration: Step 2 — Create the CI Release Pipeline The release pipeline follows five commands in sequence: create release, associate commits, upload source maps, finalize release, and record deployment. The --validate flag on source map upload checks that each .map file references a valid source file and that sourceMappingURL comments point to uploaded artifacts. Always use it in CI to catch mismatches early. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-ci-integration--d1095c