C✳CODEZ.WIN
🌐 English

Localized reading guide

sentryPurpose, usage and source

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry CLI; perform read-only queries using the sentry command.

Source retrieved:

Source repository
openai/skills
SKILL.md
skills/.curated/sentry/SKILL.md
Repository stars
28,420
Repository updated
2026-10-29
Categories
Data
Last collected

License: License file needs review

Source SKILL.md

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry CLI; perform read-only queries using the sentry command.

How the upstream workflow works

Quick start

If not already authenticated, ask the user to run sentry auth login or set SENTRY_AUTH_TOKEN as an env var. The CLI auto-detects org/project from DSNs in .env files, source code, config defaults, and directory names. Only specify / if auto-detection fails or picks the wrong target. Defaults: time range 24h, environment production, limit 20. Always use --json when processing output programmatically. Use --json --fields to select specific fields and reduce output size.

Upstream passage · L9 ↗

Core tasks (use Sentry CLI)

Use the sentry CLI for all queries. It handles authentication, org/project detection, pagination, and retries automatically. Use --json for machine-readable output.

Upstream passage · L23 ↗

1) List issues (ordered by most recent)

If auto-detection doesn't resolve org/project, pass them explicitly:

Upstream passage · L27 ↗
Upstream passage · bash ↗
sentry issue list \
  --query "is:unresolved environment:production" \
  --period 24h \
  --limit 20 \
  --json --fields shortId,title,priority,level,status

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
49f948faa9258a0c61caceaf225e179651397431
Source SHA-256
508c6f5c100586c81a34397d30f00f4b8771b66d698a7ac1836998df925dd007
Back to the full Skill catalog