Investigate Sentry Issue
Testing & Qualityinvestigate-sentry-issueInvestigate Sentry Issue is an Agent Skill for testing & quality published in the desplega-ai/agent-swarm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Investigate and triage a Sentry error issue
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/desplega-ai/agent-swarm/blob/HEAD/plugin/pi-skills/investigate-sentry-issue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/investigate-sentry-issue, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Investigate Sentry Issue
Investigate a Sentry issue to understand the error, gather context, and prepare for fixing or triaging.
Prerequisites
SENTRY_AUTH_TOKEN and SENTRY_ORG must be set. Verify with sentry-cli info.
Arguments
sentry-issue-url-or-id: A Sentry issue URL or just the issue ID (e.g.,123456)
Workflow
1. Parse the Input
If given a URL (https://sentry.io/organizations/{org}/issues/{issue_id}/), extract the issue ID.
2. Get Issue Overview
sentry-cli issues list --id <issue-id>
3. Get Detailed Info via REST API
Use https://sentry.io/api/0/organizations/${SENTRY_ORG}/issues/<issue-id>/ for metadata (first/last seen, event count, user impact, status).
4. Get Full Stacktrace
Use the recommended event endpoint: .../issues/<issue-id>/events/recommended/
Key jq paths for the response:
.entries[] | select(.type == "exception")— exception with stacktrace.entries[] | select(.type == "exception") | .data.values[].stacktrace.frames— stack frames.entries[] | select(.type == "breadcrumbs")— actions leading to the error.tags— environment, browser, OS info.context— custom context data
5. Analyze and Report
- Identify the failing file and line number
- Understand the error type and message
- Review breadcrumbs for the sequence of events
- Check tags for environment-specific issues
6. Take Action (if appropriate)
sentry-cli issues resolve <issue-id> # Resolve
sentry-cli issues mute <issue-id> # Mute
sentry-cli issues unresolve <issue-id> # Unresolve
Search Query Syntax
Use these filters with sentry-cli issues list --query:
| Filter | Example | Description |
|---|---|---|
is: | is:unresolved | Issue status |
lastSeen: | lastSeen:-2d | Seen within time range |
message: | message:undefined | Match error message |
issue.category: | issue.category:error | Error category |
Tips
- Always get the recommended event first — it's curated for debugging
- Check breadcrumbs to understand user actions before the error
- If investigating from a Slack alert, the issue URL is in the alert message