Menu
Handle Sentry issues end-to-end for SoftwareEngineer (investigate, fix, PR, and close).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | sentry-response |
| description | Handle Sentry issues end-to-end for SoftwareEngineer (investigate, fix, PR, and close). |
SENTRY_AUTH_TOKEN is set.mcp__sentry__*).# Unresolved issues in last 24h
sentry-cli issues list --project <PROJECT_SLUG> --query "is:unresolved age:-24h"
# Inspect a specific issue
sentry-cli issues info ISSUE_ID
# Resolve after merge
sentry-cli issues resolve ISSUE_ID
If only a Sentry URL is provided, extract the numeric issue ID from it.
sentry-cli to fetch the issue details and stack trace.sentry-cli was used.Create and configure role-scoped GitHub Apps for VibeTeam, map credentials to agents placeholders, and validate installation permissions/identity.
Run VibeTeam GitHub/Slack handoff validation with unit tests, Slack evals, GitHub webhook evals, and permission checks. Use when validating multi-agent GitHub communication (issues, discussions, PR comments) or when asked to prove changes via tests/evals and record status.
Create and configure VibeTeam Slack apps (one ingress app plus role-scoped responder apps), wire role tokens/secrets, and validate routing/identity behavior.
Final completion gate for VibeTeam tasks. Use at the end of implementation to verify diff quality, real testing, GitHub/Slack multi-agent communication evidence, and PR health before declaring done.
Search shared knowledgebase content using docs_tools (BM25 + fallback keyword scoring) before answering from memory.
Shared workflow for knowledgebase retrieval using docs_tools and injected OpenClaw context.