Agent skill

ops-monitor-errors

Monitor Sentry for unresolved errors in frontend and backend projects. Supports filtering by project, environment, and time range.

Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ops-monitor-errors

SKILL.md

Ops: Monitor Errors

Monitor Sentry for errors in the application.

Argument: $ARGUMENTS — project (frontend, backend, all; default: all) and optional time range (default: 1h)

Discovery

Discover Sentry configuration from:

  1. .sentryclirc — org and project names
  2. .env.* files — EXPO_PUBLIC_SENTRY_DSN for DSN
  3. package.json@sentry/react-native (frontend) or @sentry/node (backend) for project type

Sentry CLI

List Unresolved Issues

bash
sentry-cli issues list \
  --org {org} \
  --project {project}

Filter by Environment

bash
sentry-cli issues list \
  --org {org} \
  --project {project} \
  --query "is:unresolved environment:{env}"

Post-Deploy Check (new issues since deploy)

bash
sentry-cli issues list \
  --org {org} \
  --project {project} \
  --query "is:unresolved firstSeen:-{time}"

Where {time} is a Sentry duration like 1h, 30m, 24h.

Sentry API (Fallback)

If sentry-cli is not installed or not authenticated, use the API directly:

List Unresolved Issues

bash
curl -sf "https://sentry.io/api/0/projects/{org}/{project}/issues/?query=is:unresolved&sort=date" \
  -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" | \
  jq '.[] | {id: .id, title: .title, count: .count, userCount: .userCount, firstSeen: .firstSeen, lastSeen: .lastSeen}'

Filter by Environment

bash
curl -sf "https://sentry.io/api/0/projects/{org}/{project}/issues/?query=is:unresolved+environment:{env}&sort=date" \
  -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" | \
  jq '.[] | {id: .id, title: .title, count: .count, userCount: .userCount}'

Post-Deploy Workflow

After any deployment:

  1. Wait 5 minutes for errors to surface
  2. Check for new unresolved issues in the deployed environment
  3. Assess severity: are these new regressions or pre-existing?
  4. Report findings with severity assessment

Output Format

Report errors as a table:

Issue ID Title Events Users First Seen Severity
12345 TypeError: Cannot read property 'name' 42 15 5m ago HIGH
12346 Network request failed 3 2 2h ago MEDIUM

Severity Classification

Severity Criteria
CRITICAL > 100 events or > 50 users in last hour
HIGH > 10 events or > 5 users, appeared after deploy
MEDIUM Recurring issue, < 10 events
LOW < 3 events, no user impact

Include summary: total unresolved issues, new since last deploy, and recommendation (proceed / investigate / rollback).

Expand your agent's capabilities with these related and highly-rated skills.

Didn't find tool you were looking for?

Be as detailed as possible for better results