Sentry Workflow
Route to the right Sentry workflow for fixing production issues, reviewing Sentry bot comments, or upgrading SDKs.
Install
npx skills add https://github.com/getsentry/sentry-for-ai --skill sentry-workflowWhat is this skill?
- Route to fix-issues, code-review, or SDK-upgrade workflows
- Debug production exceptions with stack traces and breadcrumbs
- Resolve Sentry bot comments and predicted issues on PRs
Adoption & trust: 2k installs on skills.sh; 197 GitHub stars; 2/3 security scanners passed (skills.sh audits).
Recommended Skills
Azure Diagnosticsmicrosoft/azure-skills
Diagnosemattpocock/skills
Systematic Debuggingobra/superpowers
Safe Debuglllllllama/rigorpilot-skills
Mastramastra-ai/skills
Insforge Debuginsforge/agent-skills
Journey fit
Primary fit
This skill belongs in the operate stage because it helps teams actively manage, triage, and resolve production issues in live environments. The monitoring subphase is the right fit because Sentry workflows center on observing, diagnosing, and fixing issues discovered in production monitoring.
Common Questions / FAQ
Is Sentry Workflow safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Sentry Workflow
> [All Skills](../../SKILL_TREE.md) # 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. 1. If the user mentions **fixing errors, debugging exceptions, or investigating production issues** → `sentry-fix-issues` 2. If the user mentions **Sentry bot comments or `sentry[bot]` on a PR** → `sentry-code-review` 3. If the user mentions **Seer, bug prediction, or reviewing PRs for predicted issues** → `sentry-pr-code-review` 4. 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) | `sentry-fix-issues/SKILL.md` | | Resolving comments from `sentry[bot]` on GitHub PRs | [`sentry-code-review`](../sentry-code-review/SKILL.md) | `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) | `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) | `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](../../SKILL_TREE.md).