sentry-issue-resolver
Sentry Issue Resolver
Fetch Sentry issues with complete stack traces, analyze root causes, and provide actionable solutions using Sentry REST API.
Workflow
When the user requests Sentry issue analysis:
-
Parse the Sentry URL
- Extract org slug from subdomain (e.g.,
arcsitefromarcsite.sentry.io) - Extract issue ID from path (e.g.,
7219768209from/issues/7219768209/)
Example URL:
https://arcsite.sentry.io/issues/7219768209/?project=1730879 - Extract org slug from subdomain (e.g.,
-
Check Authentication
More from arctuition/skills
jira-ticket-creator
Create Jira tickets using jira-cli (https://github.com/ankitpokhrel/jira-cli). Use when the user asks to create Jira tickets, issues, or stories with work types (Epic/Story/Bug/A/B Test), set to Backlog status. Selects the most appropriate component from API/Projects/Proposals/Backends/Regression/AI using the -C flag. Returns the ticket URL after creation. Assumes jira-cli is already installed and configured (user has run 'jira init').
11pr-code-review
Perform GitHub pull request code reviews using the gh CLI. Use when asked to review a PR, inspect PR diffs, leave inline review comments on specific lines, or produce a priority-based summary (P0-P3) of findings with an overall correctness verdict.
10html-module-map
Produce a single-file HTML "module map" artifact that breaks down a business module, feature, subsystem, or end-to-end workflow — inline-SVG architecture diagram with the hot path highlighted, a key-files panel, a numbered callstack walkthrough in execution order, a gotchas callout, and a glossary. Use this skill whenever the user asks to break down a module, explain how a feature works, document a business workflow, draw an architecture diagram, onboard a teammate, "explain X to me", "map out the auth flow", "walk me through the order pipeline", or "document this subsystem". Trigger even without the word "HTML" — the artifact format is the whole point. For PR review use html-pr-review; for authoring a PR use html-pr-writeup.
7html-pr-review
Produce a single-file HTML "code review companion" artifact that helps a reviewer get oriented in someone else's pull request — a risk-coloured map of every file, an annotated diff with margin notes and severity tags, the call-graph that shows how the changed pieces fit together, and the questions worth asking the author. Use this skill whenever the user is about to review a PR, has been assigned one, mentions reviewing code they didn't write, says things like "help me review this", "I need to review PR #N", "what should I look at first", "I'm getting up to speed on this change", "I don't know this codebase well", or asks for a review checklist. Trigger even when the user doesn't say "HTML" — the artifact format is the whole point and the user should not have to ask for it by name. This skill is for the reviewer; if the user is the author writing their own PR description, use html-pr-writeup instead.
7html-pr-writeup
Produce a single-file HTML "PR writeup" artifact that explains a pull request to its reviewers — motivation, before/after behavior, file-by-file tour with the reasoning, where to focus the review, test plan, and rollout. Use this skill whenever the user is about to open a PR, has just finished a branch, mentions writing a PR description, asks for a PR write-up, says things like "explain this change to my team", "help me pitch this PR", "write the PR description", "summarize what I'm shipping", or wants to make sure reviewers understand intent and risk before they read the diff. Trigger even when they don't say "HTML" — the artifact format is the whole point and the user should not have to ask for it by name.
7html-thread-recap
Produce a single-file HTML "thread recap" artifact that captures what was discussed in an agent / pairing / chat conversation — the questions explored, the decisions made and their tradeoffs, the dead ends we walked into, the open questions left, and the artifacts produced — so a teammate who wasn't in the room can pick up the context. Use this skill whenever the user asks to summarize a conversation/thread/session, mentions sharing a thread with colleagues, says things like "把这个对话总结一下", "share this thread with the team", "write up what we decided", "decision log for this conversation", "document the tradeoffs we made", "recap of our pairing session", or wants to hand off a Claude/ChatGPT/agent transcript as context. Trigger even when "HTML" isn't said — the artifact format is the whole point. Input can be the current session's own conversation context OR a transcript the user pastes in.
6