playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / sentry-deploy-integration

sentry-deploy-integration skill

/plugins/saas-packs/sentry-pack/skills/sentry-deploy-integration

This skill helps you configure and monitor Sentry deployment tracking by automating release creation, source map upload, and health insights.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill sentry-deploy-integration

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.6 KB
---
name: sentry-deploy-integration
description: |
  Track deployments and releases in Sentry.
  Use when configuring deployment tracking, release health,
  or connecting deployments to error data.
  Trigger with phrases like "sentry deploy tracking", "sentry release health",
  "track deployments sentry", "sentry deployment notification".
allowed-tools: Read, Write, Edit, Bash(sentry-cli:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Sentry Deploy Integration

## Prerequisites

- Sentry CLI installed
- `SENTRY_AUTH_TOKEN` configured
- Build pipeline access
- Source maps generated during build

## Instructions

1. Create release using git SHA or semantic version with sentry-cli
2. Upload source maps from build output directory
3. Associate commits using sentry-cli releases set-commits --auto
4. Finalize the release to mark it complete
5. Deploy application to target environment
6. Notify Sentry of deployment with environment and timestamps
7. Enable session tracking for release health metrics
8. Configure environment-specific sample rates
9. Set up rollback tracking to record version changes
10. Use Sentry dashboard to compare releases and monitor health

## Output
- Releases created for each deployment
- Source maps uploaded and linked
- Deployment notifications sent
- Release health metrics tracked

## Error Handling

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

## Examples

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

## Resources
- [Sentry Releases](https://docs.sentry.io/product/releases/)
- [Release Health](https://docs.sentry.io/product/releases/health/)

Overview

This skill integrates deployment tracking and release health into Sentry to link errors with specific releases. It automates release creation, source map uploads, commit association, deployment notifications, and enables release health metrics. Use it to get clear visibility into which deployments introduced regressions and to monitor session and error trends by release.

How this skill works

The skill uses Sentry CLI workflows to create a release (by git SHA or semantic version), upload build artifacts like source maps, and associate commits automatically. After finalizing the release, it notifies Sentry of deployments with environment and timestamp metadata and enables session tracking and sampling to collect release health metrics. Outputs include created releases, uploaded source maps, deployment events, and aggregated health stats on the Sentry dashboard.

When to use it

  • Configuring CI/CD pipelines to report releases to Sentry
  • Enabling release health metrics and session tracking for new deployments
  • Linking error events to specific commits and deployments
  • Uploading source maps to improve stack trace quality
  • Tracking rollbacks and version changes across environments

Best practices

  • Install and configure SENTRY_AUTH_TOKEN in CI securely; avoid embedding tokens in code
  • Use git SHA or semantic versioning consistently so releases are uniquely identifiable
  • Upload source maps from the build output and verify paths match Sentry mappings
  • Run `sentry-cli releases set-commits --auto` to attach commits and authors for context
  • Finalize releases before notifying deployments to ensure Sentry marks the release complete
  • Configure environment-specific sample rates and enable session tracking to collect reliable health metrics

Example use cases

  • CI step that creates a Sentry release, uploads source maps, associates commits, finalizes, then notifies deployment
  • Rollout monitoring: compare health and crash-free sessions between v1.2.0 and v1.3.0 in Sentry after staging and prod deploys
  • Hotfix workflow: create a patch release with source maps, notify Sentry of deployment, and track improved error rates after rollback
  • Automated rollback tracking: pipeline notifies Sentry of version change so Sentry shows when the app reverted to a prior release

FAQ

What do I need before integrating this skill?

You need Sentry CLI installed, a configured SENTRY_AUTH_TOKEN, access to your build artifacts (source maps), and CI/CD pipeline access to run release steps.

How do I ensure source maps are useful?

Generate source maps during the build with correct path mappings, upload them for the exact release version, and verify stack frames are deobfuscated in Sentry.