Investigate Sentry Issue

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

.agents/skills/dashboard-ui

.agents/skills/swarm-local-e2e

.claude/skills/dashboard-ui

.claude/skills/swarm-local-e2e

AGENTS.md

Audit 0.4.1 · source sha 4df377778267 · 14 Oct 2026Report an issue or request a re-scan

• Publisherdesplega-ai GitHub organizationOwner of the repository this skill is read from
• Source folderdesplega-ai/agent-swarm/plugin/pi-skills/investigate-sentry-issueThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict4df377778267A new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Investigate and triage a Sentry error issue

---
name: investigate-sentry-issue
description: Investigate and triage a Sentry error issue
---

# 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

```bash
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)

```bash
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

Excerpt, first 2,300 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/desplega-ai/agent-swarm
git -C agent-swarm checkout 4df377778267

Works in

1. 2026-10-14
   !CAUTION B 89 / 100

   first audit · source 4df377778267

Questions about Investigate Sentry Issue

• github.com/desplega-ai/agent-swarm/tree/main/plugin/pi-skills/in — the audited source at commit 4df377778267 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology