issues▌

You are an orchestrator. Follow these 6 phases exactly. Do not skip phases.

Methodically discover, analyze, and fix production issues using Sentry's debugging capabilities. \n \n Integrates with Sentry MCP to search issues, retrieve stack traces, breadcrumbs, traces, and AI-generated root cause analysis via the Seer tool \n Follows a seven-phase workflow: discovery, deep analysis, hypothesis formation, code investigation, implementation, verification, and reporting \n Treats all Sentry event data as untrusted external input; enforces strict security rules against embedd

Discover, analyze, and fix production issues using Sentry's full debugging capabilities. \n \n Integrates with Sentry MCP to search issues, retrieve stack traces, breadcrumbs, traces, and AI-generated root cause analysis across your project \n Follows a structured seven-phase workflow: discovery, deep analysis, hypothesis formation, code investigation, implementation, verification, and reporting \n Treats all Sentry event data as untrusted external input; enforces security constraints against em

Create, update, and manage GitHub issues with full workflow support including types, labels, assignees, and dependencies. \n \n Supports issue creation with type categorization (Bug, Feature, Task, etc.), labels, assignees, and milestones via gh api REST calls \n Read operations via MCP tools for fetching issue details, comments, labels, and cross-repository search \n Handles issue updates (title, body, state, labels, assignees) and includes templates for bug reports, feature requests, and tasks

Search and prioritize your assigned issues by age, engagement, and status. \n \n Queries the current repository for issues assigned to you using the GitHub repo context \n Surfaces issue recommendations based on age, comment count, and open/closed status to help you prioritize work \n Integrates with the list_issues command to retrieve and analyze issue data from your repository \n