Link Sentry issues to the release that broke them.
What it does
Connects deployed application events to Sentry releases, deployment history, and suspect commits so users can identify which change introduced an issue.
When to use it
Use when setting up releases or deployment tracking, investigating what changed, or resolving unknown releases and missing suspect commits.
How to use it
Give it a project; it configures the missing Sentry release tagging, CI tracking, or suspect-commit wiring.
What you provide
- An existing project
Uses
What you need · 2
Sentry must already be installed and capturing application events; otherwise the skill directs the user to instrumentation first.
Requires a Sentry auth token stored in CI secrets and never committed; the shown files do not specify how the CI process reads it.
Access · 2
This skill
Sentry
Records releases and test events
CI
CI and deploys