Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Investigates a Jira issue that Sentry created automatically (or that links a Sentry issue): reads the Jira issue, resolves the referenced Sentry issue even when it was deleted or regrouped under a…
Install Sentry Issue
$ npx skills add shopsys/shopsys --skill sentry-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shopsys/shopsys sentry-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sentry-issue .claude/skills/sentry-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sentry-issue" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/sentry-issue into .claude/skills/sentry-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/sentry-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shopsys/shopsys --skill sentry-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shopsys/shopsys sentry-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/sentry-issue .agents/skills/sentry-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sentry-issue" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/sentry-issue into .agents/skills/sentry-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shopsys/shopsys --skill sentry-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shopsys/shopsys sentry-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/sentry-issue .cursor/skills/sentry-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sentry-issue" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/sentry-issue into .cursor/skills/sentry-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shopsys/shopsys.git --path .agents/skills/sentry-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shopsys/shopsys --skill sentry-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shopsys/shopsys sentry-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/sentry-issue .gemini/skills/sentry-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sentry-issue" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/sentry-issue into .gemini/skills/sentry-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shopsys/shopsys sentry-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shopsys/shopsys --skill sentry-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/sentry-issue .github/skills/sentry-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sentry-issue" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/sentry-issue into .github/skills/sentry-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shopsys/shopsys --skill sentry-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shopsys/shopsys sentry-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/sentry-issue .opencode/skills/sentry-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sentry-issue" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/sentry-issue into .opencode/skills/sentry-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sentry-issue- GitHub stars
- 350
- Token cost
- ~728 tokens
- SKILL.md length
- 280 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigates a Jira issue that Sentry created automatically (or that links a Sentry issue): reads the Jira issue, resolves the referenced Sentry issue even when it was deleted or regrouped under a…
- The user gives a Jira key and asks to check
- SKILL.md covers Environment delta and Reporting delta
- Calls git
- Find the cause of a Sentry error
What it does
Sentry Issue is an agent skill from shopsys/shopsys. Investigates a Jira issue that Sentry created automatically (or that links a Sentry issue): reads the Jira issue, resolves the referenced Sentry issue even when it was deleted or regrouped under a newer id, collects the evidence from Sentry (events, request, release, occurrence pattern), traces the failing frame to the code, and reports the root cause with a classification (bug / expected noise / vendor behaviour / already fixed / needs a decision) and a recommended next step. Read-only by default. Use when the…
Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Root cause analysis. It works with Sentry and Jira. The repository describes itself as: Main repository for maintaining Shopsys Platform packages. Open for ISSUES and PULL REQUESTS.
When your agent uses it
- The user gives a Jira key and asks to check
- Find the cause of a Sentry error
- Invokes /sentry-issue
Example prompts
- “Use the sentry-issue skill to investigate a Jira issue that Sentry created automatically (or that links a Sentry issue): reads the Jira issue…”
- “/sentry-issue”
What it can do on your machine
Read from SKILL.md and the folder at commit 3c4bf38. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sentry Issue loads about 728 tokens when it runs. Until then it costs about 162 tokens; SKILL.md has 280 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 280 words (~728 tokens).
“The canonical instructions for this skill are authored from the project perspective. Read them first:”
- name
- sentry-issue
- user_invocable
- true
- version
- 1.0.0
Files
Just SKILL.md in .agents/skills/sentry-issue of shopsys/shopsys.
Open the folder on GitHubat commit 3c4bf38
Compare with similar skills
Sentry Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sentry Issue this skillshopsys/shopsys | 350 | — | ~728 | Automated safety check: Pass | Custom licence | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Sentry Issue Fix Looptixl3d/tixl | 5.1k | — | ~2.1k | Automated safety check: Notes | MIT | |
| PRP Implementation PlannerWirasm/prp | 2.3k | — | ~4.1k | Automated safety check: Pass | MIT | |
| PRP PlanWirasm/prp | 2.3k | — | ~4k | Automated safety check: Pass | MIT | |
| Sentrymitsuhiko/agent-stuff | 3.2k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Sentry Issue Fix Loop
tixl3d/tixl
Walks through open Sentry issues for the tooll3 project, latest first, proposing a fix for each and committing them one at a time with your review between.
PRP Implementation Planner
Wirasm/prp
Turns a PRD, issue or description into an implementation-ready plan grounded in codebase evidence, adding root-cause analysis for bugs and publishing issue plans back to the issue.
PRP Plan
Wirasm/prp
Writes an implementation-ready plan for a feature, bug fix, refactor or chore from a PRD, issue or description, grounded in codebase evidence, and can post it back to the source issue.
Sentry
mitsuhiko/agent-stuff
Fetch and analyze Sentry issues, events, transactions, and logs.
Fix Sentry Issues
brianlovin/agent-config
Use Sentry MCP to discover, triage, and fix production issues with root-cause analysis.
More from shopsys/shopsys
All 38 skills in this repoAdhoc PR
shopsys/shopsys
Ad-hoc Pull Request Publisher — commits the current changes, pushes the branch, opens a GitHub pull request against the repository's default branch, and creates a matching SSP Jira issue in the…
Commit
shopsys/shopsys
Interactive commit workflow — analyzes all uncommitted changes, proposes atomic, logically grouped commits with messages following commit-conventions, and executes them only after the user approves…
Create Enum
shopsys/shopsys
Create a Shopsys-style enum (a class extending AbstractEnum with public typed constants, NOT a native PHP enum).
Docs Researcher
shopsys/shopsys
Searches and analyzes documentation to provide relevant information for development tasks.
PR Comments
shopsys/shopsys
Work with GitHub PR review threads — list unresolved comments as a digest (who is waiting on whom), reply to threads, and resolve/unresolve them.
PR Description
shopsys/shopsys
Generates a PR description focused on business value using the project's PR template.
Related
Categories
Questions about Sentry Issue
What does Sentry Issue do?
Investigates a Jira issue that Sentry created automatically (or that links a Sentry issue): reads the Jira issue, resolves the referenced Sentry issue even when it was deleted or regrouped under a…. Sentry Issue is an agent skill from shopsys/shopsys. Investigates a Jira issue that Sentry created automatically (or that links a Sentry issue): reads the Jira issue, resolves the referenced Sentry issue even when it was deleted or regrouped under a newer id, collects the evidence from Sentry (events, request, release, occurrence pattern), traces the failing frame to the code, and reports the root cause with a classification (bug / expected noise / vendor behaviour / already fixed / needs a decision) and a recommended next step.
When should I use Sentry Issue?
Sentry Issue fits situations like: the user gives a Jira key and asks to check; find the cause of a Sentry error; invokes /sentry-issue.
How do I install Sentry Issue in Claude Code?
Run `npx skills add shopsys/shopsys --skill sentry-issue -a claude-code`. Or copy the skill folder (.agents/skills/sentry-issue in shopsys/shopsys) into .claude/skills/sentry-issue in your project. Claude Code loads it when a task matches its description.
How do I install Sentry Issue in Codex?
Run `npx skills add shopsys/shopsys --skill sentry-issue -a codex`. Or copy the skill folder (.agents/skills/sentry-issue in shopsys/shopsys) into .agents/skills/sentry-issue in your project. Codex loads it when a task matches its description.
Can I use Sentry Issue in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shopsys/shopsys --skill sentry-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-issue, .gemini/skills/sentry-issue, .github/skills/sentry-issue and .opencode/skills/sentry-issue in your project.
What does Sentry Issue need to run?
Going by SKILL.md and its folder, Sentry Issue needs the command-line tools its instructions call (git).
Does Sentry Issue access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Sentry Issue safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sentry Issue use?
Sentry Issue has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Sentry Issue use?
About 728 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sentry Issue?
Skills that share tags, products or a category with Sentry Issue: Code Design Rationale Investigator (cursor/plugins, 10k stars), Sentry Issue Fix Loop (tixl3d/tixl, 5.1k stars), PRP Implementation Planner (Wirasm/prp, 2.3k stars) and PRP Plan (Wirasm/prp, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sentry Issue?
shopsys (a GitHub organization) maintains it in shopsys/shopsys, which has 350 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 7, 2026.
Source: shopsys/shopsys on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.