Agent skill · software engineering · pedronauck
sentry-cli
Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
Why this skill is useful
Provides specific commands and workflows for interacting with Sentry's API that the AI wouldn't reliably generate on its own.
What it needs
Requires sentry installed locally. Requires sentry account access. About 12k tokens when loaded. Last updated 2026-08-01. 564 stars on the source repository.
What this skill does
Sentry CLI Usage Guide Help users interact with Sentry from the command line using the sentry CLI. Core rule for agents: just run the command. The sentry CLI auto-detects your org and project (from .sentryclirc, DSNs in .env/source, and the directory name), so do not list organizations and then list their projects to work out which one this checkout maps to — that manual discovery only duplicates work the CLI already does on every command. Pass an explicit <org>/<project> only when the CLI reports it can't detect the target or picks the wrong one. Agent Guidance Best practices and operational guidance for AI coding agents using the Sentry CLI. Key Principles Just run the command — the CLI handles authentication and org/project detection automatically. Don't pre-authenticate or look up org/project before running commands. The CLI prompts for login if needed. Prefer CLI commands over raw API calls — the CLI has dedicated commands for most tasks. Reach for sentry issue view, sentry issue list, sentry trace view, etc. before constructing API calls manually or fetching external documentation. Use sentry docs for setup questions — if you need to know how to configure a Sentry SDK or feature, run sentry docs "your question" to query the documentation directly. This is faster and more accurate than fetching docs externally. Use sentry schema to explore the API — if you need to discover API endpoints, run sentry schema to browse interactively or sentry schema <resource> to search. This is faster than fetching OpenAPI specs externally. Use sentry issue view <id> to investigate issues — when asked about a specific issue (e.g., CLI-G5, PROJECT-123), use sentry issue view directly. Use --json for machine-readable output — pipe through jq for filtering. Human-readable output includes formatting that is hard to parse. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pedronauck/sentry-cli