Agent SkillsAgent Skills
Brmbobo

sentry-upgrade-migration

@Brmbobo/sentry-upgrade-migration
Brmbobo
1
0 forks
Updated 4/1/2026
View on GitHub

Execute upgrade Sentry SDK and migrate between versions. Use when upgrading Sentry SDK, handling breaking changes, or migrating from legacy versions. Trigger with phrases like "upgrade sentry", "sentry migration", "update sentry sdk", "sentry breaking changes".

Installation

$npx agent-skills-cli install @Brmbobo/sentry-upgrade-migration
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Path.claude/agents/enterprise-frontend-design/agents/saas-packs/sentry-pack/skills/sentry-upgrade-migration/SKILL.md
Branchmaster
Scoped Name@Brmbobo/sentry-upgrade-migration

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

npx agent-skills-cli list

Skill Instructions


name: sentry-upgrade-migration description: | Execute upgrade Sentry SDK and migrate between versions. Use when upgrading Sentry SDK, handling breaking changes, or migrating from legacy versions. Trigger with phrases like "upgrade sentry", "sentry migration", "update sentry sdk", "sentry breaking changes". allowed-tools: Read, Write, Edit, Bash(npm:*), Grep version: 1.0.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io

Sentry Upgrade Migration

Prerequisites

  • Current Sentry SDK version identified
  • Target version changelog reviewed
  • Non-production environment for testing
  • Test suite for error capture and performance monitoring

Instructions

  1. Check current SDK version with npm list or pip show
  2. Review release notes and changelog for target version
  3. Back up current Sentry configuration file
  4. Update package to target version in non-production first
  5. Run tests to identify breaking changes
  6. Update deprecated APIs following migration guide patterns
  7. Verify error capture works with test error
  8. Verify performance monitoring works with test transaction
  9. Deploy to staging and monitor for issues
  10. Deploy to production after staging validation

Output

  • SDK upgraded to target version
  • Breaking changes resolved
  • Code updated for new APIs
  • Error capture verified working

Error Handling

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

Examples

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

Resources

More by Brmbobo

View all
firecrawl-reliability-patterns
1

Implement FireCrawl reliability patterns including circuit breakers, idempotency, and graceful degradation. Use when building fault-tolerant FireCrawl integrations, implementing retry strategies, or adding resilience to production FireCrawl services. Trigger with phrases like "firecrawl reliability", "firecrawl circuit breaker", "firecrawl idempotent", "firecrawl resilience", "firecrawl fallback", "firecrawl bulkhead".

clay-observability
1

Set up comprehensive observability for Clay integrations with metrics, traces, and alerts. Use when implementing monitoring for Clay operations, setting up dashboards, or configuring alerting for Clay integration health. Trigger with phrases like "clay monitoring", "clay metrics", "clay observability", "monitor clay", "clay alerts", "clay tracing".

visualization-best-practices
1

Manage visualization best practices operations. Auto-activating skill for Data Analytics. Triggers on: visualization best practices, visualization best practices Part of the Data Analytics skill category. Use when working with visualization best practices functionality. Trigger with phrases like "visualization best practices", "visualization practices", "visualization".

exa-local-dev-loop
1

Configure Exa local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Exa. Trigger with phrases like "exa dev setup", "exa local development", "exa dev environment", "develop with exa".