From lisa-expo
Monitor Sentry for unresolved errors in frontend and backend projects. Supports filtering by project, environment, and time range.
npx claudepluginhub codyswanngt/lisa --plugin lisa-expoThis skill is limited to using the following tools:
Monitor Sentry for errors in the application.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Monitor Sentry for errors in the application.
Argument: $ARGUMENTS — project (frontend, backend, all; default: all) and optional time range (default: 1h)
Discover Sentry configuration from:
.sentryclirc — org and project names.env.* files — EXPO_PUBLIC_SENTRY_DSN for DSNpackage.json — @sentry/react-native (frontend) or @sentry/node (backend) for project typesentry-cli issues list \
--org {org} \
--project {project}
sentry-cli issues list \
--org {org} \
--project {project} \
--query "is:unresolved environment:{env}"
sentry-cli issues list \
--org {org} \
--project {project} \
--query "is:unresolved firstSeen:-{time}"
Where {time} is a Sentry duration like 1h, 30m, 24h.
If sentry-cli is not installed or not authenticated, use the API directly:
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}'
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}'
After any deployment:
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 | 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).