메뉴
Sentry issue triage and investigation with automatic cross-linking. Handles issue investigation, AI analysis via Seer, and integration with Linear for tracking fixes. Use when triaging Sentry errors, investigating sentry.io URLs, or creating Linear issues from Sentry.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate professional documentation for IntexuraOS services (apps, workers, packages). Produces 5 doc files per service, 3 per package, plus aggregated site content and cross-validation reports. Supports interactive, autonomous, and team-of-agents modes. Use when documenting services, generating docs, updating documentation, or validating doc consistency.
Orchestrate a 6-phase release workflow with automated service documentation, high-level docs updates, README "What's New" section, website improvements, and semantic versioning. Use when preparing a new release.
Prepare an IntexuraOS release by collecting release data, triaging changes, updating docs, versions, changelog, website release highlights, and GitHub release notes.
Use when the user says "commit push", "commit and push", "push a PR", or asks Codex to finalize IntexuraOS changes by committing, pushing, and opening a pull request against development.
Use when user pastes a dev.intexuraos.cloud or intexuraos.cloud code-task URL and asks to debug, investigate, or understand what went wrong. Also use when user mentions a code task ID (task_*) with investigation intent.
Autonomous PR comment triage - fixes review feedback until CI passes
| name | sentry |
| description | Sentry issue triage and investigation with automatic cross-linking. Handles issue investigation, AI analysis via Seer, and integration with Linear for tracking fixes. Use when triaging Sentry errors, investigating sentry.io URLs, or creating Linear issues from Sentry. |
| argument-hint | [sentry-url | analyze <url> | linear <url> | triage --limit N] |
Triage, investigate, and resolve Sentry issues with enforced cross-linking to Linear and GitHub.
Organization: intexuraos-dev-pbuchman
/sentry # NON-INTERACTIVE: Triage unresolved issues
/sentry <sentry-url> # Investigate specific issue
/sentry INT-123 # Find Sentry issues linked to Linear issue
/sentry triage --limit 5 # Batch triage with limit
/sentry analyze <sentry-url> # AI-powered root cause analysis via Seer
pnpm run ci:tracked MUST pass before PR creationThe skill automatically detects intent from input:
| Input Pattern | Type | Workflow |
|---|---|---|
/sentry (no args) | Batch Triage | triage-batch.md |
/sentry <sentry-url> | Single Issue | triage-issue.md |
/sentry analyze <url> | Seer Analysis | analyze-with-seer.md |
/sentry linear <sentry-url> | Create Linear | create-linear-issue.md |
/sentry triage --limit N | Limited Batch | triage-batch.md |
Before ANY operation, verify all required tools:
| Tool | Verification Command | Purpose |
|---|---|---|
| Sentry MCP | mcp__sentry__whoami | Issue management |
| Linear MCP | mcp__linear__list_teams | Issue tracking |
| GitHub CLI | gh auth status | PR creation |
| GCloud | Service account verification | Firestore access |
Service account key location: ~/.config/gcloud/sa-key.json
gcloud auth list shows no active account, activate service accountYou are NEVER "unauthenticated" if the service account key file exists.
If ANY required tool is unavailable, ABORT immediately:
ERROR: /sentry cannot proceed - <tool-name> unavailable
Required for: <purpose>
Fix: <fix-command>
Aborting.
Issues are fetched from these Sentry projects:
intexuraos-development (backend services)intexuraos-web-development (web app)Every Sentry issue must be traceable across all systems:
| Direction | Method |
|---|---|
| Sentry → Linear | Comment on Sentry with Linear issue link |
| Linear → Sentry | [sentry] <title> naming + link in description |
| Linear → GitHub | PR title contains INT-XXX |
| GitHub → Linear | Fixes INT-XXX in PR body |
| GitHub → Sentry | Sentry link in PR description |
workflows/templates/reference/