codyswanngt/ops-monitor-errors
plugins/lisa-expo-copilot/skills/ops-monitor-errors/SKILL.md
Monitor Sentry for unresolved errors in frontend and backend projects. Supports filtering by project, environment, and time range.
$ install --global
skillsauthnpx skillsauth add codyswanngt/lisa ops-monitor-errorsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 12, 2026, 3:01 AM4.7s1 file scanned
SKILL.md
- name:
- ops-monitor-errors
- description:
- Monitor Sentry for unresolved errors in frontend and backend projects. Supports filtering by project, environment, and time range.
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:
.sentryclirc— org and project names.env.*files —EXPO_PUBLIC_SENTRY_DSNfor DSNpackage.json—@sentry/react-native(frontend) or@sentry/node(backend) for project type
Sentry CLI
List Unresolved Issues
sentry-cli issues list \
--org {org} \
--project {project}
Filter by Environment
sentry-cli issues list \
--org {org} \
--project {project} \
--query "is:unresolved environment:{env}"
Post-Deploy Check (new issues since deploy)
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
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
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:
- Wait 5 minutes for errors to surface
- Check for new unresolved issues in the deployed environment
- Assess severity: are these new regressions or pre-existing?
- 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).
Related Skills
codyswanngt/lisa-setup-workstation
development
VerifiedTrustedCommunity
Prepare a machine — a fresh laptop or a throwaway container — to run coding agents, before any repository exists. Detects which of Lisa's supported agents (Claude Code, Codex, Cursor, OpenCode, Antigravity, Copilot) are already installed, asks which credential manager the machine uses (Bitwarden, 1Password, Doppler, Vault, AWS, or none), and installs only what is missing, each by its vendor's own preferred method. Idempotent, headless by default, and emits a Dockerfile for a spin-up/spin-down environment. Run it on a new machine, in a container, or before cloning anything.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-remote-env
tools
VerifiedTrustedCommunity
Provision and verify a remote execution environment for a host project — Codex Cloud today, other remote surfaces as they are added. Generates a repository-owned setup script that installs the declared toolchain, materializes secrets through lisa-secrets-access, and runs the project's own hook. Provisions by API where one exists, by driving the vendor console where one does not, and by emitting exact config otherwise — then proves the result with the same read-back regardless of which tier did the work. Use before dispatching any work with executionEnv.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-setup-local-env
tools
VerifiedTrustedCommunity
Bring a developer's machine in line with the toolchain the project declares. Reports every tool in remoteEnv.tools that is missing, outdated, or unpinned for this platform, and installs the missing ones into ~/.local/bin from the same pinned, checksummed entries the remote surfaces use — but only when asked. Same manifest, same pins, same installers as lisa-setup-remote-env; what differs is consent and that the pin is a floor rather than an equality. Run it on a fresh checkout, after a manifest change, or when a tool fails at the moment of use.
3SKILL.mdUpdated Aug 30, 2026
codyswanngt/lisa-remote-dispatch
tools
VerifiedTrustedCommunity
Route one unit of work to a remote execution surface. Reads the executionEnv parameter (local by default, codex-cloud or claude-web today), verifies the environment is provisioned and bound to this repository, submits a thin skill invocation, records the task identifier to .lisa/remote-dispatch.json, and exits without polling. Routing only — the remote runs the identical skill from the identical repository. Composable and inline: other skills invoke it via the Skill tool rather than users calling it directly.
3SKILL.mdUpdated Aug 30, 2026