Skip to content
Back to skills

Sentry Ci Integration

ASecurity

Manage integrate Sentry with CI/CD pipelines. Use when setting up GitHub Actions, GitLab CI, or other CI systems with Sentry releases and source maps. Trigger with phrases like "sentry github actions", "sentry CI", "sentry pipeline", "automate sentry releases".

  • 2,688 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 7, 2026
devopsbashgitci/cd

Works with

  • cli

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned February 10, 2026

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill sentry-ci-integration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sentry Ci Integration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sentry Ci Integration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jeremylongshore-sentry-ci-integration/badge)](https://www.skillsdirectory.com/skills/jeremylongshore-sentry-ci-integration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sentry-ci-integration
description: |
  Manage integrate Sentry with CI/CD pipelines.
  Use when setting up GitHub Actions, GitLab CI, or other CI systems
  with Sentry releases and source maps.
  Trigger with phrases like "sentry github actions", "sentry CI",
  "sentry pipeline", "automate sentry releases".
allowed-tools: Read, Write, Edit, Bash(gh:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
---

# Sentry Ci Integration

## Prerequisites

- Sentry CLI installed or available in CI
- `SENTRY_AUTH_TOKEN` secret configured
- `SENTRY_ORG` and `SENTRY_PROJECT` environment variables set
- Source maps generated during build

## Instructions

1. Add SENTRY_AUTH_TOKEN secret to CI platform (GitHub, GitLab, CircleCI)
2. Configure SENTRY_ORG and SENTRY_PROJECT environment variables
3. Create workflow step to build application with SENTRY_RELEASE env
4. Add step to create Sentry release using sentry-cli or action
5. Upload source maps from build output directory
6. Associate commits with release using set-commits --auto
7. Finalize the release to mark it complete
8. Add deploy notification step for environment tracking
9. Configure checkout with fetch-depth: 0 for full git history
10. Test workflow by pushing to trigger release creation

## Output
- Release created and finalized in Sentry
- Source maps uploaded for stack trace mapping
- Commits associated with release
- Deploy notification sent to Sentry

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources
- [Sentry CI/CD](https://docs.sentry.io/product/releases/setup/release-automation/)
- [GitHub Action](https://github.com/getsentry/action-release)

Files in this skill

  • SKILL.md1.8 KB
  • references/circleci.md704 B
  • references/errors.md467 B
  • references/examples.md207 B
  • references/github-actions.md1.3 KB
  • references/gitlab-ci.md653 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.