Official agent skill

Sentry Backend Bugs

Review Sentry Python and Django changes for bug patterns drawn from real production issues.

OfficialCustom licenceAuto-check: notesBackend & APIs

Install Sentry Backend Bugs

skills CLI

$ npx skills add getsentry/sentry --skill sentry-backend-bugs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install getsentry/sentry sentry-backend-bugs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sentry-backend-bugs .claude/skills/sentry-backend-bugs && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "sentry-backend-bugs" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/sentry-backend-bugs into .claude/skills/sentry-backend-bugs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-backend-bugs", 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

$skill-installer install https://github.com/getsentry/sentry/tree/master/.agents/skills/sentry-backend-bugs

Type 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.

skills CLI

$ npx skills add getsentry/sentry --skill sentry-backend-bugs -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install getsentry/sentry sentry-backend-bugs --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/sentry-backend-bugs .agents/skills/sentry-backend-bugs && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sentry-backend-bugs" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/sentry-backend-bugs into .agents/skills/sentry-backend-bugs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-backend-bugs", 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.

skills CLI

$ npx skills add getsentry/sentry --skill sentry-backend-bugs -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install getsentry/sentry sentry-backend-bugs --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/sentry-backend-bugs .cursor/skills/sentry-backend-bugs && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sentry-backend-bugs" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/sentry-backend-bugs into .cursor/skills/sentry-backend-bugs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-backend-bugs", 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

$ gemini skills install https://github.com/getsentry/sentry.git --path .agents/skills/sentry-backend-bugs

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add getsentry/sentry --skill sentry-backend-bugs -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install getsentry/sentry sentry-backend-bugs --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/sentry-backend-bugs .gemini/skills/sentry-backend-bugs && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "sentry-backend-bugs" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/sentry-backend-bugs into .gemini/skills/sentry-backend-bugs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-backend-bugs", 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.

GitHub CLI

$ gh skill install getsentry/sentry sentry-backend-bugs

Installs 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).

skills CLI

$ npx skills add getsentry/sentry --skill sentry-backend-bugs -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/sentry-backend-bugs .github/skills/sentry-backend-bugs && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "sentry-backend-bugs" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/sentry-backend-bugs into .github/skills/sentry-backend-bugs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-backend-bugs", 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.

skills CLI

$ npx skills add getsentry/sentry --skill sentry-backend-bugs -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install getsentry/sentry sentry-backend-bugs --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/getsentry/sentry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/sentry-backend-bugs .opencode/skills/sentry-backend-bugs && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sentry-backend-bugs" agent skill from https://github.com/getsentry/sentry/tree/master/.agents/skills/sentry-backend-bugs into .opencode/skills/sentry-backend-bugs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-backend-bugs", 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-backend-bugs
GitHub stars: 45k
Token cost: ~3.5k tokens
SKILL.md length: 1,668 words
Files: 10 (incl. references)
Skills in repo: 29
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

Review Sentry Python and Django changes for bug patterns drawn from real production issues.

Works in 3 steps: Classify the Code → Check for Top Bug Patterns → Report Findings
Reviewing a backend diff
SKILL.md covers Scope, Step 1: Classify the Code, Step 2: Check for Top Bug… and Step 3: Report Findings
Calls python; needs HTTP_X_GITLAB_TOKEN and HTTP_X_EVENT_KEY

What it does

Sentry Backend Bugs is an agent skill from getsentry/sentry, published by the product's own GitHub organization. Review Sentry Python and Django changes for bug patterns drawn from real production issues. Use when reviewing a backend diff or PR, checking Warden findings, auditing the current branch, reviewing production-error patterns, or looking for common regressions in src/ and tests/.

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `README.md`, `references/concurrency-bugs.md` and `references/data-validation.md`).

It sits in Backend & APIs, covering Backend development. It works with Sentry, Django and Python. The repository describes itself as: Developer-first error tracking and performance monitoring.

When your agent uses it

Reviewing a backend diff
Checking Warden findings
Auditing the current branch
Reviewing production-error patterns

Example prompts

“/sentry-backend-bugs”

Requirements

Python 3
A credential in HTTP_X_GITLAB_TOKEN
A credential in HTTP_X_EVENT_KEY
Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Classify the Code
Check for Top Bug Patterns
Report Findings

What it can do on your machine

Read from SKILL.md and the folder at commit 87d1203. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Grep
- Glob
- Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- HTTP_X_GITLAB_TOKEN
- HTTP_X_EVENT_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sentry Backend Bugs loads about 3.5k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 1,668 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~3.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~20k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Grep, Glob, Bash
```

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 1,668 words (~3,535 tokens).

“Find bugs in Sentry backend code by checking for the patterns that cause the most real production errors.”

— opening of SKILL.md by getsentry, Custom licence

name: sentry-backend-bugs
allowed-tools: Read, Grep, Glob, Bash

Outline of SKILL.md

Sentry Backend Bug Pattern Review
Scope
Step 1: Classify the Code
Step 2: Check for Top Bug Patterns
Check 1: Metric Subscription Query Errors -- 113 issues, 3,035,640 events
Check 2: Missing Record / Stale Reference -- 81 issues, 1,403,592 events
Check 3: Search Query Validation -- 57 issues, 2,001,330 events
Check 4: Value Validation Errors -- 45 issues, 1,000,624 events
Check 5: Type Errors -- 28 issues, 740,106 events
Check 6: Internal API Request Errors -- 71 issues, 829,753 events
Check 7: Database Constraint Violations -- 22 issues, 2,962,198 events
Check 8: Data Parsing & Deserialization -- 19 issues, 272,812 events
Check 9: Missing Key Access (KeyError) -- 25 issues, 155,020 events
Check 10: Concurrency and Runtime Bugs -- 23 issues, 38,443 events
Check 11: Logic Correctness -- not pattern-based
Step 3: Report Findings

Read the full SKILL.md on GitHub

Files

SKILL.md and 9 other files (references) in .agents/skills/sentry-backend-bugs of getsentry/sentry.

SKILL.md
README.md
references/concurrency-bugs.md
references/data-validation.md
references/database-integrity.md
references/integration-errors.md
references/missing-records.md
references/null-and-type-errors.md
references/query-validation.md
references/url-safety.md

Open the folder on GitHubat commit 87d1203

Compare with similar skills

Sentry Backend Bugs 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.

Sentry Backend Bugs compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sentry Backend Bugs this skillgetsentry/sentry	45k	—	~3.5k	Automated safety check: Notes	Custom licence	today
Sentry Python SDKgetsentry/sentry-for-ai	268	—	~4.1k	Automated safety check: Pass	Apache-2.0	today
Django Access Reviewgetsentry/skills	1k	3 repos	~2.6k	Automated safety check: Notes	Apache-2.0	4 days ago
Silk Profilerbaserow/baserow	6.1k	—	~2.9k	Automated safety check: Pass	Custom licence	today
Django Run Locallyfossasia/eventyay	1.7k	—	~411	Automated safety check: Pass	Apache-2.0	today
Fix Slow Endpointvpcarlos/profyle	123	—	~2.1k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Sentry Python SDK
getsentry/sentry-for-ai
Official
Full Sentry SDK setup for Python. An agent skill from getsentry/sentry-for-ai.
268 GitHub stars~4.1k tokensUpdated today
Backend & APIsAuto-check passed
Django Access Review
getsentry/skills
Official
Django access control and IDOR security review. An agent skill from getsentry/skills.
1k GitHub starsUsed in 3 repos~2.6k tokens
Backend & APIsAuto-check: notes
Silk Profiler
baserow/baserow
Investigate backend performance using Django Silk profiling data.
6.1k GitHub stars~2.9k tokensUpdated today
Backend & APIsAuto-check passed
Django Run Locally
fossasia/eventyay
Steps for initiating the Django development server without Docker
1.7k GitHub stars~411 tokensUpdated today
Backend & APIsAuto-check passed
Fix Slow Endpoint
vpcarlos/profyle
Diagnose and fix a slow endpoint or request in a Python web app (FastAPI, Flask, Django, Tornado, any ASGI/WSGI framework) using real Profyle/VizTracer traces, then prove the fix by replaying the…
123 GitHub stars~2.1k tokensUpdated 2 days ago
Backend & APIsAuto-check passed
Liveserver
mathiasertl/django-ca
Start a local Django development server and make HTTP requests against it for interactive endpoint testing
158 GitHub stars~977 tokensUpdated 3 days ago
Backend & APIsAuto-check passed

Questions about Sentry Backend Bugs

What does Sentry Backend Bugs do?

Review Sentry Python and Django changes for bug patterns drawn from real production issues. Sentry Backend Bugs is an agent skill from getsentry/sentry, published by the product's own GitHub organization. Review Sentry Python and Django changes for bug patterns drawn from real production issues.

When should I use Sentry Backend Bugs?

Sentry Backend Bugs fits situations like: reviewing a backend diff; checking Warden findings; auditing the current branch; reviewing production-error patterns.

How do I install Sentry Backend Bugs in Claude Code?

Run `npx skills add getsentry/sentry --skill sentry-backend-bugs -a claude-code`. Or copy the skill folder (.agents/skills/sentry-backend-bugs in getsentry/sentry) into .claude/skills/sentry-backend-bugs in your project. Claude Code loads it when a task matches its description.

How do I install Sentry Backend Bugs in Codex?

Run `npx skills add getsentry/sentry --skill sentry-backend-bugs -a codex`. Or copy the skill folder (.agents/skills/sentry-backend-bugs in getsentry/sentry) into .agents/skills/sentry-backend-bugs in your project. Codex loads it when a task matches its description.

Can I use Sentry Backend Bugs 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 getsentry/sentry --skill sentry-backend-bugs -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-backend-bugs, .gemini/skills/sentry-backend-bugs, .github/skills/sentry-backend-bugs and .opencode/skills/sentry-backend-bugs in your project.

What does Sentry Backend Bugs need to run?

Going by SKILL.md and its folder, Sentry Backend Bugs needs the command-line tools its instructions call (python) and credentials named HTTP_X_GITLAB_TOKEN and HTTP_X_EVENT_KEY. Our summary lists: Python 3; A credential in HTTP_X_GITLAB_TOKEN; A credential in HTTP_X_EVENT_KEY. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash.

Does Sentry Backend Bugs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sentry Backend Bugs safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Sentry Backend Bugs use?

Sentry Backend Bugs 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 Backend Bugs use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.

What are the alternatives to Sentry Backend Bugs?

Skills that share tags, products or a category with Sentry Backend Bugs: Sentry Python SDK (getsentry/sentry-for-ai, 268 stars), Django Access Review (getsentry/skills, 1k stars), Silk Profiler (baserow/baserow, 6.1k stars) and Django Run Locally (fossasia/eventyay, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sentry Backend Bugs?

getsentry (a GitHub organization, an official publisher) maintains it in getsentry/sentry, which has 45,495 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.

Source: getsentry/sentry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Sentry Backend Bugs

Install Sentry Backend Bugs

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Sentry Python SDK

Django Access Review

Silk Profiler

Django Run Locally

Fix Slow Endpoint

Liveserver

More from getsentry/sentry

Scraps Review

Analytics

Hybrid Cloud Outboxes

Hybrid Cloud Rpc

Hybrid Cloud Test Gen

Lint Fix

Questions about Sentry Backend Bugs

Install Sentry Backend Bugs

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

More from getsentry/sentry

Related

Questions about Sentry Backend Bugs