القائمة
View a Sentry issue by short ID (e.g. PROJECT-123) or URL. Shows details, status, latest event, and tag distribution. Use when user wants to view, check, or look up a Sentry issue, error, or event.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate a single-file HTML artifact (status report, slide deck, prototype, throwaway editor, flowchart, etc.) and open it in the browser. Use when the user wants a one-off visual artifact instead of markdown — for sharing, reference, or interactive exploration.
Gather context from the codebase and (optionally) the web, then propose multiple ways to move forward with tradeoffs, relative impact, and effort. Use when user wants to explore options, weigh approaches, or asks "what are my options" / "how should I tackle this" before committing to a plan.
Propose a concrete plan to cut a branch and implement a change as one or more atomic commits, grounded in the current codebase and (optionally) outside research. Use when user wants a step-by-step implementation plan, asks "propose a plan" / "how would you implement this", or is ready to move from discussion to execution.
Summarize what shipped over a date range, commit range, or release tag — synthesizes git log, GitHub PRs, and Linear issues into a single markdown brief.
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
| name | view-sentry |
| description | View a Sentry issue by short ID (e.g. PROJECT-123) or URL. Shows details, status, latest event, and tag distribution. Use when user wants to view, check, or look up a Sentry issue, error, or event. |
| argument-hint | <issue short ID or URL> |
| allowed-tools | mcp__sentry__get_sentry_resource, mcp__sentry__search_issue_events, mcp__sentry__get_issue_tag_values, mcp__sentry__find_organizations |
View and summarize the Sentry issue specified by $ARGUMENTS.
Default organizationSlug is remilia-corporation (region URL https://us.sentry.io). Use this without calling find_organizations. Only fall back to find_organizations if the user explicitly references a different org or this default fails.
$ARGUMENTS is a Sentry URL (e.g. https://<org>.sentry.io/issues/PROJECT-123/ or https://sentry.io/organizations/<org>/issues/...) → pass it through as url to get_sentry_resource (org is encoded in the URL)$ARGUMENTS is a short ID like PROJECT-123 → use as resourceId with resourceType='issue' and the default org slug above$ARGUMENTS is an event ID (32-char hex) → use resourceType='event' with the default org slugUse mcp__sentry__get_sentry_resource:
url=<the URL> (resource type auto-detected)resourceType='issue', organizationSlug=<slug>, resourceId='PROJECT-123'Use mcp__sentry__search_issue_events to get recent occurrences:
issueUrl=<URL> OR issueId='PROJECT-123' organizationSlug=<slug>query='' (or a filter like environment:production)limit=5This surfaces stack traces, environments, and timestamps for the most recent events.
If the issue is widespread or the user wants impact analysis, use mcp__sentry__get_issue_tag_values for relevant tags:
tagKey='environment' — which envs are affectedtagKey='release' — which releasestagKey='url' or tagKey='browser' — for frontend issuesSkip this for trivial or single-event issues.
Status: status | Level: level | Assignee: name (if any) Project: project | Platform: platform First seen: timestamp | Last seen: timestamp Events: count | Users affected: count
Brief summary of the error message and culprit (file:line or transaction).
(Only if fetched in Step 4.)
The Sentry URL for quick navigation.