Sentry Fix Verification
SkillMonitoring & opsThis skill verifies that a bug fix actually worked once it shipped. Your AI can connect a code change and its release to the matching Sentry issue and compare error activity before and after the release. Issues only get marked resolved when the data backs it up, not on guesswork.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the skill, then ask your AI to verify a fix by naming the Sentry issue and the release that shipped the change. It will compare event activity before and after the release and tell you whether the fix is holding.
Then ask your AI: use the Sentry Fix Verification skill
What your AI can do with it
- Check whether a Sentry issue is truly fixed after a release
- Compare event trends before and after a release
- Link a code change and its release to the Sentry issue's current state
- Review post-release event trends for a fix
- Hold off on resolving an issue until the data supports it
What this skill tells your AI
The instructions your AI receives, as published by devin-axis/ipollowork in examples/plugin-packages/sentry/skills/sentry-fix-verification/SKILL.md and read by ahel’s review.
- Record the target issue, expected fix, code change, release, environment, and observation window.
- Confirm the release containing the change is actually present in Sentry.
- Compare post-release events and affected users with the pre-release baseline.
- Report whether evidence shows fixed, improving, unchanged, regressed, or insufficient traffic.
- Change issue state only when the user requests it and the verification evidence is adequate.
Keep local tests, merged code, deployed release, and observed production behavior as separate milestones.
Signals
- GitHub stars
- 6k
- Forks
- 1k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
sentry-fix-verification- Source
- github.com/devin-axis/ipollowork