bug-investigatelisted

# bug-investigate ## Instructions ### 1. Auto-detect ticket from branch Run `git branch --show-current` and extract ticket IDs: - Match pattern: `[A-Z]+-[0-9]+` (e.g., `DEV-1234`, `PROJ-567`) - Common branch formats: `fix/DEV-1234/description`, `hotfix/DEV-999`, `fix/bug-description` If a ticket ID is found: ``` 🔀 Branch: {branch-name} 🎫 Ticket detected: {TICKET-ID} > 1. Yes — load ticket > 2. No — skip ``` If yes → fetch via Jira API and show summary (see step 2). If no ticket found → continue to step 2. ### 2. Ask for bug sources ``` 🐛 Bug Investigation What information do you have? (multiple allowed) 1. 🎫 Jira ticket(s) — provide key(s) (e.g. DEV-1234) 2. 🔴 Sentry issue — provide URL or issue ID 3. 💬 Bug description — describe the bug manually 4. 📋 Error message — paste error message or stacktrace ``` Accept **multiple sources** — the more context, the better. ### 3. Gather context from each source **Jira ticket (if provided):** - Fetch via Jira API (`/issue/{key}`). - Extract: title, description, priority, status, comments, linked issues. - Check for linked Sentry issues in comments or description. ``` 🎫 Jira: {KEY} — {title} Status: {status} | Priority: {priority} Description: {summary} Comments: {count} ({key points}) Sentry links: {extracted URLs or "none found"} ``` **Sentry issue (if provided):** - Use `get_issue_details` with the URL or issue ID. - Use `get_issue_tag_values` for environment, browser, URL distribution. ``