chore: Add sentry issue slash command (#375)

.pi/prompts/sentry-issue.md

@@ -0,0 +1,60 @@
+---
+description: Pick or fix a Sentry issue end-to-end, then PR and watch CI
+argument-hint: "[issue-id-or-url]"
+---
+Run Sentry issue repair workflow for this project only.
+
+Input: `$ARGUMENTS`
+
+Goal:
+1. Use provided Sentry issue id or URL. If none provided, choose the highest-impact unresolved issue using frequency, affected users, recency, and production impact.
+2. Create/switch to git branch named exactly after the Sentry short issue id.
+3. Investigate root cause, implement fix, and add/update tests.
+4. Open PR and watch CI until green.
+
+Rules:
+- Protect local work. Start with `git status --short`. If uncommitted changes exist, stop and ask before branching.
+- Never expose secrets. Do not print tokens, `.env`, Sentry auth, DB URLs, or PII.
+- Use Sentry MCP tools first: `find_organizations`, `find_projects`, `search_issues`, `get_sentry_resource`, `search_issue_events`, `get_issue_tag_values`, `get_replay_details`, `get_profile_details`, `analyze_issue_with_seer` when root cause unclear.
+- For Laravel ecosystem changes, use `application-info` and `search-docs` before code changes.
+- Activate/read relevant project skills when touched: Pest tests, Inertia React, Wayfinder, Tailwind, Fortify, Pennant.
+- Every code change needs programmatic verification. Add or update a focused Pest/test when feasible. Run minimum affected tests. Run `vendor/bin/pint --dirty --format agent` after PHP edits.
+- Prefer small surgical fix. No dependency changes without approval.
+
+Workflow:
+1. Identify issue:
+   - If `$ARGUMENTS` is a Sentry URL, fetch it with `get_sentry_resource(url=...)`.
+   - If `$ARGUMENTS` is a bare issue id, discover org/project if needed, then fetch issue with `get_sentry_resource(resourceType="issue", resourceId=<id>, organizationSlug=<org>)`.
+   - If no args, find org/project, search unresolved production issues with both frequency and user sorting, compare top results, and pick one with best impact score: high event count, high user count, recent lastSeen, production environment, clear actionable stack.
+   - Record chosen short issue id and Sentry URL in notes.
+2. Branch:
+   - Derive branch name from Sentry short issue id only, e.g. `WHISPER-MONEY-123`.
+   - Run `git switch -c <issue-id>`; if branch exists, `git switch <issue-id>`.
+3. Investigate:
+   - Fetch latest events, stack trace, breadcrumbs, environment, release, tags, URLs/routes, affected users count, and relevant traces/replays/profiles if present.
+   - Reproduce locally using tests or focused command. Inspect app logs/browser logs if relevant.
+   - If root cause not obvious after issue/event data, run Seer analysis.
+4. Fix:
+   - Read nearby code and conventions first.
+   - Implement minimal fix.
+   - Add regression test covering Sentry failure path.
+5. Verify:
+   - Run targeted test command, e.g. `php artisan test --compact --filter=<test-or-class>`.
+   - Run lint/format commands required by touched files.
+   - If failures occur, fix and rerun until pass.
+6. PR:
+   - Commit changes with concise conventional commit.
+   - Push branch.
+   - Create PR with `gh pr create`, including Sentry issue link, root cause, fix summary, and verification commands.
+   - Get PR number from `gh pr view --json number --jq .number` if needed.
+   - Watch CI every 10 seconds with `gh pr checks <number> --watch --fail-fast --interval 10`.
+   - If CI fails, inspect logs, fix, commit/push, and watch again until green.
+
+Output when done:
+- Issue id + Sentry URL
+- Branch name
+- Root cause
+- Fix summary
+- Tests/commands run
+- PR URL
+- CI status