hebertzhu Sentry
Intent
- Use for read-only Sentry issue inspection, error summarization, event lookups, and lightweight production-health triage.
Default operating pattern
- Confirm scope first: organization, project, environment, time range, and whether the user wants issue lists, issue detail, or event detail.
- Prefer the current host's Sentry connector if it exists; otherwise use
scripts/sentry_api.pywith a locally configuredSENTRY_AUTH_TOKEN. - Read before summarizing: list issues first, then drill into a specific issue or event only when needed.
- Redact sensitive data and avoid dumping raw stack traces unless the user explicitly asks for deeper debugging detail.
- Return a clear operational summary: what is happening, how severe it looks, and which issue or event should be investigated next.
Bundled helper
scripts/sentry_api.pyprovides deterministic, read-only Sentry API calls for issues and events.
Pack fit
- Included in:
knowledge-ops - Keep the public version read-only, reproducible, and safe for production support workflows.
Boundary
- Do not request users to paste tokens into chat; ask them to set
SENTRY_AUTH_TOKENlocally. - Do not mutate Sentry state or claim root cause unless the issue or event evidence supports it.