OpenParable
Skip to content
← Back to skills

Investigate Sentry Issue

Testing & Quality
investigate-sentry-issue

Investigate 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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
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

  1. Identify the failing file and line number
  2. Understand the error type and message
  3. Review breadcrumbs for the sequence of events
  4. 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:

FilterExampleDescription
is:is:unresolvedIssue status
lastSeen:lastSeen:-2dSeen within time range
message:message:undefinedMatch error message
issue.category:issue.category:errorError 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