npx skills add ...
npx skills add getsentry/sentry-docs --skill commit
npx skills add getsentry/sentry-docs --skill commit
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.
Follow these conventions when creating commits for Sentry projects.
Before committing, always check the current branch:
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 the user whether to create a branch; just proceed with branch creation. The create-branch skill will still propose a branch name for the user to confirm.
Use the create-branch skill to create the branch. After create-branch completes, verify the current branch has changed before proceeding:
If still on main or master (e.g., the user aborted branch creation), stop — do not commit.
The header is required. Scope is optional. All lines must stay under 100 characters.
| Type | Purpose |
|---|---|
feat | New feature |
fix | Bug fix |
ref | Refactoring (no behavior change) |
perf | Performance improvement |
docs | Documentation only |
test | Test additions or corrections |
build | Build system or dependencies |
ci | CI configuration |
chore | Maintenance tasks |
style | Code formatting (no logic change) |
meta | Repository metadata |
license | License changes |
Reference issues in the footer using these patterns:
Fixes closes the issue when mergedRefs links without closingWhen changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer:
This 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.
feat(alerts): Add Slack thread replies for alert updates
When an alert is updated or resolved, post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped together.
Refs GH-1234ref: Extract common validation logic to shared module
Move duplicate validation code from three endpoints into a shared
validator class. No behavior change.feat(api)!: Remove deprecated v1 endpoints
Remove all v1 API endpoints that were deprecated in version 23.1.
Clients should migrate to v2 endpoints.
BREAKING CHANGE: v1 endpoints no longer available
Fixes SENTRY-9999revert: feat(api): Add new endpoint
This reverts commit abc123def456.
Reason: Caused performance regression in production.