Conventional commit messages
Commits in Sentry's Conventional Commits style: a feature branch instead of main, a typed capitalised subject up to 70 characters, Fixes or Refs footers, no personal data. Use when asked to commit changes or draft a commit message.
commit- Author
- Sentry
- Source
- getsentry/skills/skills/commit @ a582c51
- License
- Apache-2.0 · Copyright 2025 Functional Software, Inc. dba Sentry
About this skill
What it does
The skill makes the agent commit the way Sentry's repositories do. First it checks the branch: on main or master it creates a feature branch unless you asked for a direct commit, then checks again and stops if it is still there. Each commit is one coherent change that can be reviewed on its own.
Messages follow Conventional Commits with Sentry's details: <type>(<scope>): <subject>, scope optional, ! before the colon for a breaking change. The subject is imperative, capitalised, without a trailing period and at most 70 characters; every line stays under 100. Types come from a fixed list: feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license, revert — ref for refactoring, style for formatting, meta for repository metadata. The optional body explains what changed and why. Footers: Fixes <issue> closes an issue on merge, Refs <issue> only links it, BREAKING CHANGE: states the impact. Customer names, emails, ticket contents, secrets and other personal data never go into a message.
The commit is made with one -m per paragraph or footer, never with a literal \n or an interactive editor. The folder holds only SKILL.md and the licence.
When to use it, and when not
Its description claims every request to commit or draft a commit message, so once installed it handles all commits.
That is the catch: it does not read git log for an existing convention. In a repository with lowercase subjects, ticket keys or no type prefixes, it writes Sentry-style messages unless you say otherwise. It also says nothing about which files to stage.
How to run it
The install command below puts the folder in place. The agent picks the skill up by its description whenever you ask to commit; to call it yourself:
- Claude Code:
/commit, or ask for the skill by name. - Codex:
$commit. - Cursor: type
/in the Agent chat and pickcommit.
Example: /commit Commit the parser fix on a new branch and reference issue #431 without closing it.
How it differs from similar skills
Commit message writer from our catalog reads git log, follows the repo's existing convention and commits only when asked. Git workflow and versioning is a broad git policy with its own <type>: <description> format, using refactor where Sentry uses ref. PR title and description writer from the same pack uses the same type list for PR titles, so commits and PRs match.
Install
Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.
curl -fsSL --create-dirs -o ~/.claude/skills/commit/SKILL.md https://anymodel.org/en/skills/sentry/commit/SKILL.md -o ~/.claude/skills/commit/LICENSE https://anymodel.org/en/skills/sentry/commit/LICENSE
curl -fsSL --create-dirs -o ~/.agents/skills/commit/SKILL.md https://anymodel.org/en/skills/sentry/commit/SKILL.md -o ~/.agents/skills/commit/LICENSE https://anymodel.org/en/skills/sentry/commit/LICENSE
foreach ($f in 'SKILL.md','LICENSE') { $p = Join-Path "$HOME\.claude\skills\commit" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/sentry/commit/$f" -UseBasicParsing -OutFile $p }foreach ($f in 'SKILL.md','LICENSE') { $p = Join-Path "$HOME\.agents\skills\commit" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/sentry/commit/$f" -UseBasicParsing -OutFile $p }Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/sentry/commit/SKILL.md
SKILL.md
Sentry Commit Messages
Before Committing
git branch --show-current
If the branch is main or master, create a feature branch unless the user
explicitly requested a direct commit. Re-check the branch and stop if it is
still main or master.
Commit one coherent, independently reviewable change at a time.
Message Rules
Use:
<type>(<scope>): <subject>
<optional body>
<optional footer>
- Scope is optional. Add
!before:for a breaking change. - Write the subject in imperative, present tense; capitalize it, omit the trailing period, and keep it at 70 characters or fewer.
- Keep every line under 100 characters.
- Use the body only when useful. Explain what changed and why, including previous behavior or motivation when it helps.
- Never include customer or organization names, user emails, support ticket contents, secrets, or PII. Describe the technical symptom instead.
Allowed types: feat, fix, ref, perf, docs, test, build,
ci, chore, style, meta, license, and revert.
Use ref for refactoring without behavior changes, style for formatting
without logic changes, and meta for repository metadata.
Footers
Fixes <issue>closes an issue when merged.Refs <issue>links an issue without closing it.- For breaking changes, add
BREAKING CHANGE: <impact>.
Creating the Commit
Use separate -m arguments for paragraphs and footers. Never put literal
\n sequences in a commit message or open an interactive editor.
git commit -m "fix(api): Handle null response in user endpoint" \
-m "Return 404 when the user API finds a deleted account." \
-m "Fixes SENTRY-5678"
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel