sentry-prod-checklist

Production deployment checklist for Sentry integration.Use when preparing for production deployment, reviewingSentry configuration, or verifying production readiness.Trigger with phrases like "sentry production", "deploy sentry","sentry checklist", "sentry go-live".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

This Claude skill provides a comprehensive production deployment checklist for Sentry integration, designed to ensure robust error tracking and application stability. It guides developers through critical production-readiness steps, including DSN configuration, source map uploads, and alert rule optimization, helping teams minimize downtime and accelerate debugging in live environments.

Use Cases

  • Pre-Launch Production Audit: Use this skill to verify that your Sentry configuration is fully optimized and secure before a major production release.
  • CI/CD Pipeline Integration: Ensure source maps are correctly generated and uploaded via sentry-cli to maintain readable stack traces for minified production code.
  • Incident Response Setup: Configure team notification channels and alert rules to establish a proactive monitoring workflow and reduce Mean Time to Resolution (MTTR).
  • Security and Privacy Compliance: Verify that PII (Personally Identifiable Information) scrubbing is active and debug modes are disabled to meet production security standards.
namesentry-prod-checklist
description|
allowed-toolsRead, Grep, Bash(npm:*), Bash(curl:*)
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Sentry Prod Checklist

Prerequisites

  • Sentry account with project created
  • Production DSN separate from development/staging
  • Build pipeline with source map generation
  • sentry-cli installed and configured with auth token

Instructions

  1. Configure production DSN via environment variables (never hardcode)
  2. Set environment to "production" and configure release version
  3. Generate source maps during build process
  4. Upload source maps using sentry-cli releases commands
  5. Verify security settings (sendDefaultPii: false, debug: false)
  6. Configure appropriate sample rates for production volume
  7. Set up alert rules with team notification channels
  8. Connect source control and issue tracker integrations
  9. Run verification test to confirm error capture and source maps
  10. Document rollback procedure for emergency disable

Output

  • Production-ready Sentry configuration
  • Verified source map uploads
  • Configured alert rules and notifications
  • Documented release workflow
  • Validated error capture with test events

Error Handling

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

Examples

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

Resources