Sentry Regression Monitoring

SkillMonitoring & ops

This skill lets your AI compare Sentry error data across releases and time windows. Once added, your AI can spot new issues, regressions, and shifts in error frequency or user impact, so problems are caught soon after a release instead of later.

Available today. Use it from your connected AI after setup.

After adding the skill, ask your AI to compare error data between two releases or time windows. It will report what is new, what regressed, and where user impact changed.

Then ask your AI: use the Sentry Regression Monitoring skill

What your AI can do with it

  • Identify new issues that appear in a release
  • Detect regressions by comparing one release against another
  • Track changes in how often errors occur
  • Spot spikes in user impact
  • Compare error data across bounded time windows

What this skill tells your AI

The instructions your AI receives, as published by devin-axis/ipollowork in examples/plugin-packages/sentry/skills/sentry-regression-monitoring/SKILL.md and read by ahel’s review.

  1. Confirm the projects, environments, releases, and comparison windows.
  2. Compare new, regressed, and materially changed issues using counts and affected-user evidence.
  3. Exclude known test, development, and irrelevant environments unless requested.
  4. Rank findings by user impact and confidence, not raw event count alone.
  5. Return links or identifiers and state gaps caused by sampling or missing release data.

Do not treat correlation with a release as proof of causation.

Signals

GitHub stars
6k
Forks
1k
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
sentry-regression-monitoring
Source
github.com/devin-axis/ipollowork