Menu
Investigate and fix a Sentry issue in this codebase. Use when the user provides a Sentry issue URL or ID and wants diagnosis, a fix, verification, or a PR.
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
Interact with the Fizzy tracker for Pagecord work. Use when the user asks to list, create, update, move, close, comment on, or inspect Fizzy cards, boards, tags, users, steps, pins, or notifications.
Apply core Ruby on Rails best practices for architecture, naming, RESTful routing, authorisation, safety, and maintainability. Use by default for Rails coding, refactoring, debugging, feature implementation, migrations, controller/model changes, and code review tasks so baseline standards stay consistent.
Run the local CI sequence for this repo. Use when the user asks to run CI, verify a branch before push, or check code quality with the full local pipeline.
Review Ruby and Rails code as a principal engineer. Use when the user asks for a code review, PR review, diff review, or wants risks, regressions, security issues, Rails idiom problems, UI state issues, or test gaps identified before merging.
Interact with the Pagecord API for a blog. Use when the user wants to inspect posts or pages, publish content through the API, check API connectivity, or inspect the home page.
Interact with Cloudflare R2 buckets used by Pagecord. Use when the user wants to list objects, inspect bucket stats, fetch files, or check backup integrity in R2.
| name | sentry |
| description | Investigate and fix a Sentry issue in this codebase. Use when the user provides a Sentry issue URL or ID and wants diagnosis, a fix, verification, or a PR. |
| allowed-tools | Bash, Read, Grep |
sentry-cli first when it is installed and authenticated. Fall back to other Sentry tools only if the CLI is unavailable.sentry-cli --version before calling Sentry.sentry-cli info; issue investigation needs read scopes such as org:read, project:read, and event:read.org:ci, ask the user to run sentry-cli login or otherwise configure a read-capable token locally. Never ask the user to paste an auth token in chat.pagecord. Infer the issue ID from a Sentry URL like https://pagecord.sentry.io/issues/7528519207.sentry-cli issues list requires both org and project. Use it to confirm an issue is visible when the project slug is known:sentry-cli issues list --org pagecord --project <project-slug> --id <issue-id> --max-rows 5
sentry-cli events list for recent project events when the project slug is known:sentry-cli events list --org pagecord --project <project-slug> --max-rows 20 --show-tags
issues info, issues events, or api. For issue details, stack traces, per-issue events, spans, and breadcrumbs, call Sentry's read-only API with curl using the token from the local Sentry CLI config. Never echo the token:TOKEN=$(awk -F= '/token/ { gsub(/[[:space:]]/, "", $2); print $2 }' ~/.sentryclirc)
curl -fsS -H "Authorization: Bearer $TOKEN" -H "Accept: application/json" \
"https://sentry.io/api/0/issues/<issue-id>/"
curl -fsS -H "Authorization: Bearer $TOKEN" -H "Accept: application/json" \
"https://sentry.io/api/0/issues/<issue-id>/events/?limit=5"
curl -fsS -H "Authorization: Bearer $TOKEN" -H "Accept: application/json" \
"https://sentry.io/api/0/projects/pagecord/<project-slug>/events/<event-id>/"
jq to extract only the fields needed for diagnosis.metadata, culprit, transaction, breakdowns, span entries, breadcrumbs, and render partial identifiers rather than pasting raw event JSON.sentry-cli projects list --org pagecord
sentry-<issue-id> when starting an implementation task.fix/sentry-<issue-id> instead.