What this agent helps you do
A Sentry and GitHub bugfix handoff agent moves from production error to implementation plan. Sentry supplies issue evidence, stack traces, affected users, release context, and event frequency, while GitHub supplies source code, pull requests, issues, tests, and review history.
When to use this workflow
Use it for on-call triage, customer-impacting bugs, release regressions, support escalations, or any issue where production evidence needs to become a ready-to-build task.
How Sentry and GitHub give the agent context
Connect both plugins and provide the Sentry issue, release, or error cluster plus the relevant repository. Sentry should show the production symptom; GitHub should help turn it into a fixable task. Make acceptance criteria explicit before code changes.
Example starter prompt
Analyze this Sentry issue, inspect relevant GitHub repository context, and prepare a bugfix handoff with likely cause, affected files, reproduction notes, tests to add, and rollback considerations.Suggested workflow steps
Start with Sentry impact and stack traces. Have the agent identify the error path, release, and environment, then inspect GitHub for recent changes, owning files, tests, and related issues that may explain the failure.
Expected handoff
Ask for likely cause, affected files, reproduction notes, suggested fix approach, tests to add, rollback considerations, and acceptance criteria.