agentleFS
Sign inStart free
abdullahkhawerabdullahkhawer/devops-skills/skills/sentry-cli/SKILL.md

sentry-cli

Skill8 starsChanged 6 months agoApache-2.0View on GitHub

Perform Sentry error tracking operations using the sentry-cli tool and Sentry HTTP API. Use for querying issues, events, releases, and organizations.

  • Installs packages

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the configuration and rules below when constructing all sentry-cli/API commands.

    line 8
  2. Distinctive:

    Update the table below with your Sentry organization and credential file paths:

    line 12
  3. Distinctive:

    If the target environment is unclear, ask the user before running any command.

    line 19
  4. Distinctive:

    NEVER target an organization/project not listed in the configuration table above.

    line 74
  5. Very specific:

    NEVER print, display, log, or store the contents of any token file or SENTRY_AUTH_TOKEN value.

    line 75
  6. Very specific:

    Always read the token inline ($(cat <TOKEN_FILE>)) — never hardcode it in a command or shell profile.

    line 76
  7. Distinctive:

    NEVER delete a release, issue, or project without explicit user instruction — these are irreversible.

    line 77
  8. Distinctive:

    NEVER change issue status (resolve/ignore) in bulk without explicit user instruction.

    line 78
  9. Very specific:

    All list endpoints are paginated via the Link response header — follow the next relation until absent to fetch all pages.

    line 79

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sentry CLI Skill

Use the configuration and rules below when constructing all sentry-cli/API commands.

Configuration

Update the table below with your Sentry organization and credential file paths:

EnvironmentOrganizationProjectToken File
Production<your-org-slug><your-prod-project-slug>~/.sentry/prod.token
Staging<your-org-slug><your-staging-project-slug>~/.sentry/staging.token

If the target environment is unclear, ask the user before running any command.

Prerequisites (one-time setup by user)

Generate a Sentry auth token (Settings → Auth Tokens) with project:read/org:read scope for each environment and save it to the corresponding token file. Never print or display token values. Do not perform these steps yourself.

brew install getsentry/tools/sentry-cli
mkdir -p ~/.sentry && echo "<your-auth-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE>

Command Format

Via sentry-cli:

SENTRY_AUTH_TOKEN="$(cat <TOKEN_FILE>)" sentry-cli --org <org-slug> <command>

Via API (curl), for operations sentry-cli doesn't cover:

curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
  "https://sentry.io/api/0/<endpoint>" | jq .

Available Commands / Endpoints

Read-only (safe, no confirmation needed)

Command / EndpointDescription
sentry-cli releases list --org <org> -p <project>List releases
sentry-cli releases info <version> --org <org> -p <project>Show release details
/api/0/projects/<org>/<project>/issues/List issues
/api/0/issues/<id>/Get a specific issue
/api/0/issues/<id>/events/List events for an issue
/api/0/organizations/<org>/projects/List projects in the org

Mutating operations (confirm with user before running)

Command / EndpointDescription
sentry-cli releases new <version>Create a new release
sentry-cli releases deploys <version> newRegister a deploy for a release
/api/0/issues/<id>/ (PUT)Update issue status (resolve, ignore, assign)

Never run — requires explicit human approval

Command / EndpointReason
sentry-cli releases delete <version>Irreversible release deletion
/api/0/issues/<id>/ (DELETE)Irreversible issue deletion
/api/0/projects/<org>/<project>/ (DELETE)Irreversibly deletes the entire project

Rules

  • NEVER target an organization/project not listed in the configuration table above. If a command references an unfamiliar org or project, stop and ask the user to confirm.
  • NEVER print, display, log, or store the contents of any token file or SENTRY_AUTH_TOKEN value.
  • Always read the token inline ($(cat <TOKEN_FILE>)) — never hardcode it in a command or shell profile.
  • NEVER delete a release, issue, or project without explicit user instruction — these are irreversible.
  • NEVER change issue status (resolve/ignore) in bulk without explicit user instruction.
  • All list endpoints are paginated via the Link response header — follow the next relation until absent to fetch all pages.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free