Menu
Use when debugging production issues, stack traces, incidents, releases, or regressions using Sentry data.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Explore options, trade-offs, and decision paths without implementing code. Use when the user asks to brainstorm, compare approaches, choose architecture, or save a durable decision note.
Plan and implement safe schema, migration, relationship, index, query, and backfill changes with rollback awareness. Use when data shape or persistence contracts change.
Manage deployment, Docker, CI/CD, environment, secrets, and infrastructure changes with rollback and verification. Use for operational config or release safety work.
Create, update, and audit durable project documentation. Use when code, setup, workflow, architecture, API behavior, or project structure must be reflected in docs.
Implement planned product or code changes phase by phase using repo patterns and verification. Use when the user asks to build, modify, or finish implementation work.
Coordinate multi-specialist work, handoffs, blockers, and durable progress artifacts. Use when tasks span roles, phases, or parallel workstreams.
| name | mcp-sentry |
| description | Use when debugging production issues, stack traces, incidents, releases, or regressions using Sentry data. |
Use this skill when a task needs production error context from Sentry, including issues, stack traces, release impact, or recent regressions.
Only use this skill if the Sentry MCP tools are available in the current assistant. If they are not available, say that Sentry is not configured and continue with local evidence only.
