ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
Add this skill
npx mdskills install getsentry/commitComprehensive commit message formatting guide with clear rules, multiple examples, and branching prereqs.
1---2name: commit3description: ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.4---56# Sentry Commit Messages78Follow these conventions when creating commits for Sentry projects.910## Prerequisites1112Before committing, always check the current branch:1314```bash15git branch --show-current16```1718**If you're on `main` or `master`, you MUST create a feature branch first** — unless the user explicitly asked to commit to main. Do not ask for confirmation; default to creating the branch.1920```bash21# Create and switch to a new branch22git checkout -b <type>/<short-description>23```2425Branch naming should follow the pattern: `<type>/<short-description>` where type matches the commit type (e.g., `feat/add-user-auth`, `fix/null-pointer-error`, `ref/extract-validation`).2627## Format2829```30<type>(<scope>): <subject>3132<body>3334<footer>35```3637The header is required. Scope is optional. All lines must stay under 100 characters.3839## Commit Types4041| Type | Purpose |42|------|---------|43| `feat` | New feature |44| `fix` | Bug fix |45| `ref` | Refactoring (no behavior change) |46| `perf` | Performance improvement |47| `docs` | Documentation only |48| `test` | Test additions or corrections |49| `build` | Build system or dependencies |50| `ci` | CI configuration |51| `chore` | Maintenance tasks |52| `style` | Code formatting (no logic change) |53| `meta` | Repository metadata |54| `license` | License changes |5556## Subject Line Rules5758- Use imperative, present tense: "Add feature" not "Added feature"59- Capitalize the first letter60- No period at the end61- Maximum 70 characters6263## Body Guidelines6465- Explain **what** and **why**, not how66- Use imperative mood and present tense67- Include motivation for the change68- Contrast with previous behavior when relevant6970## Footer: Issue References7172Reference issues in the footer using these patterns:7374```75Fixes GH-123476Fixes #123477Fixes SENTRY-123478Refs LINEAR-ABC-12379```8081- `Fixes` closes the issue when merged82- `Refs` links without closing8384## AI-Generated Changes8586When changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer:8788```89Co-Authored-By: Claude <noreply@anthropic.com>90```9192This is the only indicator of AI involvement that should appear in commits. Do not add phrases like "Generated by AI", "Written with Claude", or similar markers in the subject, body, or anywhere else in the commit message.9394## Examples9596### Simple fix9798```99fix(api): Handle null response in user endpoint100101The user API could return null for deleted accounts, causing a crash102in the dashboard. Add null check before accessing user properties.103104Fixes SENTRY-5678105Co-Authored-By: Claude <noreply@anthropic.com>106```107108### Feature with scope109110```111feat(alerts): Add Slack thread replies for alert updates112113When an alert is updated or resolved, post a reply to the original114Slack thread instead of creating a new message. This keeps related115notifications grouped together.116117Refs GH-1234118```119120### Refactor121122```123ref: Extract common validation logic to shared module124125Move duplicate validation code from three endpoints into a shared126validator class. No behavior change.127```128129### Breaking change130131```132feat(api)!: Remove deprecated v1 endpoints133134Remove all v1 API endpoints that were deprecated in version 23.1.135Clients should migrate to v2 endpoints.136137BREAKING CHANGE: v1 endpoints no longer available138Fixes SENTRY-9999139```140141## Revert Format142143```144revert: feat(api): Add new endpoint145146This reverts commit abc123def456.147148Reason: Caused performance regression in production.149```150151## Principles152153- Each commit should be a single, stable change154- Commits should be independently reviewable155- The repository should be in a working state after each commit156157## References158159- [Sentry Commit Messages](https://develop.sentry.dev/engineering-practices/commit-messages/)160
Full transparency — inspect the skill content before installing.