Sentry Workflows
Debug production issues and maintain code quality with Sentry context. This page helps you find the right workflow skill for your task.
How to Fetch Skills
Use curl to download skills — they are 10–20 KB files that fetch tools often summarize, losing critical details.
curl -sL https://skills.sentry.dev/sentry-fix-issues/SKILL.md
Append the path from the Path column in the table below to https://skills.sentry.dev/. Do not guess or shorten URLs.
Start Here — Read This Before Doing Anything
Do not skip this section. Do not assume which workflow the user needs. Ask first.
- If the user mentions fixing errors, debugging exceptions, or investigating production issues →
sentry-fix-issues - If the user mentions Sentry bot comments or
sentry[bot]on a PR →sentry-code-review - If the user mentions Seer, bug prediction, or reviewing PRs for predicted issues →
sentry-pr-code-review - If the user mentions upgrading Sentry, migrating SDK versions, or fixing deprecated APIs →
sentry-sdk-upgrade
When unclear, ask the user whether the task involves live production issues, PR review comments, or SDK upgrades. Do not guess.
Workflow Skills
| Use when | Skill | Path |
|---|---|---|
| Finding and fixing production issues — stack traces, breadcrumbs, event data | sentry-fix-issues | sentry-fix-issues/SKILL.md |
Resolving comments from sentry[bot] on GitHub PRs | sentry-code-review | sentry-code-review/SKILL.md |
| Fixing issues detected by Seer Bug Prediction in PR reviews | sentry-pr-code-review | sentry-pr-code-review/SKILL.md |
| Upgrading the Sentry JavaScript SDK — migration guides, breaking changes, deprecated APIs | sentry-sdk-upgrade | sentry-sdk-upgrade/SKILL.md |
Each skill contains its own detection logic, prerequisites, and step-by-step instructions. Trust the skill — read it carefully and follow it. Do not improvise or take shortcuts.
Looking for SDK setup or feature configuration instead? See the full Skill Tree.