---
name: sentry
description: "Check Sentry for unresolved issues and run triage on demand. Triggered by requests to check Sentry errors, run Sentry triage, or handle Sentry issues."
allowed-tools: Bash
user-invocable: true
argument-hint: "[--apply]"
---

# Sentry Triage

Run the Sentry triage pipeline on demand. Classifies all unresolved issues (A–E), files GitHub issues for actionable bugs, and sends a Telegram summary.

## Classification

| Class | Label      | Action                                     |
|-------|------------|--------------------------------------------|
| A     | Noise      | Test/mock/harness errors → Sentry ignored  |
| B     | Transient  | Rate limits, network errors → archived     |
| C     | Actionable | Real bugs (≥10 events) → GitHub issue      |
| D     | Review     | Ambiguous → listed for human review        |
| E     | Stale      | No events in 30 days → Sentry resolved     |

## Apply Mode

By default the triage runs **dry-run** — it classifies and reports but does not file GitHub issues or change Sentry state.

Pass `--apply` to enable live writes:

```
/sentry --apply
```

## How to Run

The `SENTRY_TRIAGE_APPLY` env var controls live writes (default `0` = dry-run;
`1` = files GitHub issues + updates Sentry state):

```bash
cd ~/src/ai && python -c "
from reflections.sentry_triage import run_sentry_triage
result = run_sentry_triage()
print(result['summary'])
if result['status'] != 'disabled':
    show = False
    for line in result.get('findings', []):
        if line.startswith('Class C') or line.startswith('Class D'):
            show = True
        elif line.startswith('Class '):
            show = False
        if show:
            print(line)
"
```

For live mode, run the same command prefixed with `SENTRY_TRIAGE_APPLY=1`.

## Argument Handling

Check the user's invocation for `--apply`. If present, use the live mode command. Otherwise use dry-run.

If the user says "apply changes", "file the issues", "do it for real", or similar — first run the dry-run to show what will be actioned, state the count explicitly ("This will file N GitHub issues and update M Sentry issues"), then ask for confirmation before running live mode.

## After Running

- Show the summary line (counts by class).
- Show all Class C items — these are the actionable bugs.
- Show Class D items — note that only the top 5 are listed even if more exist.
- Omit Class A/B/E details unless the user asks.

If running dry-run and Class C issues exist, offer: "Run `/sentry --apply` to file GitHub issues for the N actionable bugs."