Sentry errors resolved before your team sees them
Agents monitor Sentry for new errors, investigate root causes in the codebase, propose fixes, create pull requests, and even deploy patches — all automatically. Wake up to fixed bugs, not new tickets.
What you get
Sentry issues detected and prioritized automatically. The agent checks for new errors, ranks them by frequency and user impact, and focuses on what matters most.
The agent reads stacktraces, finds the relevant source code, traces the bug through the codebase, and identifies the root cause — not just the symptom.
Code changes proposed with clear explanations. Each pull request includes a description of the bug, the root cause, and why the fix works.
The agent flags what it can't confidently fix — providing investigation notes, likely root cause, and recommended next steps for your team to review.
Recurring daily runs catch regressions immediately. Bugs introduced yesterday are investigated and fixed today — before they compound into bigger problems.
Schedule it daily. The agent checks Sentry overnight, investigates errors, creates PRs for fixable bugs, and drops a summary in Slack before your team's morning standup.
> Found 12 new issues — prioritizing by frequency & impact
Investigating top 5 errors:
> #1 TypeError in /api/payments — reading stacktrace, tracing source
> #2 ConnectionError in /api/sync — identifying retry logic gap
> #3 ValidationError in /api/users — null check missing on input
> #4 RangeError in /lib/pagination — off-by-one in cursor calc
> #5 TimeoutError in /api/export — needs architectural review
Results:
> Fixed 3 of 5 errors — PRs created with explanations
> Flagged 2 errors for human review — investigation notes attached
✓ PR #412: Fix null pointer in payment processing
✓ PR #413: Add retry logic for sync connection errors
✓ PR #414: Add input validation for user endpoint
✓ Summary posted to #engineering on Slack
For CRHQ clients
Enable the required skills
Make sure these skills are active on your satellite:
Connect Sentry and define your workflow
Example prompt:
Schedule daily runs
Set up a recurring daily schedule so the agent triages bugs overnight. New errors are investigated and fixed before your team starts work each morning. Use the schedule skill to automate it.
Get more out of this workflow
Pair with automated code review
Once the agent creates a PR, have another agent (or the same one) run automated code review to check the fix for quality, test coverage, and potential side effects. This creates a double-check before any human reviews the change.
Enforce project standards with coding-best-practices
The coding-best-practices skill ensures every fix follows your project's coding standards — naming conventions, error handling patterns, test requirements, and documentation. Fixes that don't meet the bar are flagged before the PR is created.
coding-best-practicesDelegate complex investigations to sub-agents
For bugs that span multiple services or require deep codebase exploration, use the delegation skill to spawn specialized sub-agents. One agent traces the frontend, another traces the API, and a third checks the database layer — all coordinated by a lead agent.
delegationBuild a knowledge base with investigation notes
Store investigation notes in project documents so future triage runs can reference past findings. Over time, the agent builds institutional knowledge about your codebase — common failure patterns, fragile areas, and recurring issues.