Use Sentry Skills to submit code changes by the spec

Who it is for

This skill is for Sentry staff, to load the team's Agent Skills in a coding assistant. It follows the open Agent Skills format. Notes:

https://agentskills.io/

It is not a public general Sentry product tutorial. The better use is: you are already changing code in Sentry-related repositories and want the assistant to work by these skills, especially when submitting changes. If you are not a user of that team workflow, the skills may include conventions that only make sense internally.

Repository page:

https://github.com/getsentry/skills

First try in 3 minutes

The official install command is only this one:

npx skills add getsentry/skills

Before running it, confirm you want it in the current assistant. Do not also run a second install command from a plugin marketplace. The page says it works with several compatible assistants, but do not read the example roster as the only supported range.

After install, if you use Claude Code, restart once as the notes say, so the skills auto-enable when related tasks appear. The first run is a low-risk check: open the commit skill notes, learn that submits must go through it, and do not run git commit on a real repository yet.

Commit skill notes:

https://github.com/getsentry/skills/blob/main/skills/commit/SKILL.md

Success signal: the assistant can find that skill and cites it when you mention submitting, instead of giving a bare git commit.

Use cases

Case 1: After install, wait for auto-enable. Evidence says skills auto-enable when a related task is detected; on Claude Code you need a restart after install. Ask a read-only question whether Sentry skills are loaded. Do not change product code for this.

Case 2: Submit changes through the commit skill. Evidence says code-change submits must use that skill and must never bypass it to commit directly. First have the assistant check the intended commit message by that skill, and only truly submit after you agree. The first time you can stop at “generate and check the commit message”, and leave the real commit until you confirm.

Limits

These skills are for Sentry staff. Code submits must go through the commit skill.

The first run uses only the npx install. The page also has a Claude plugin-marketplace install command; do not write it as a parallel main path. The restart note appears after install and only matters in environments that need a restart to load skills.

The cited notes do not list operation steps for every child skill. Do not invent missing internal flows. Do not commit directly without going through the commit skill.