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.

Sentry Commit Messages Follow these conventions when creating commits for Sentry projects. When to Use The user asks to commit code, prepare a commit message, or save changes in git. You need Sentry style commit formatting with conventional commit structure and issue references. The task requires enforcing branch safety before committing, especially avoiding direct commits on main or master . Prerequisites 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 and the server permits direct pushes. A user request does not bypass protected branch rules; when the remote rejects direct updates, use the repository's required pull request path. 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. Format The header is required. Scope is optional. All lines must stay under 100 characters. Commit Types 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 Subject Line Rules Use imperative, present tense: "Add feature" not "Added feature" Capitalize the first letter No period at the end Maximum 70 characters Body Guidelines Explain what and why , not how Use imperative mood and present tense Include motivation for the change Contrast with previous behavior when relevant Footer: Issue References Reference issues in the footer using these patterns: Fixes closes the issue when merged Refs links without closing AI Generated Changes When 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. Examples Simple fix Feature with scope Refactor Breaking change Revert Format Principles Each commit should be a single, stable change Commits should be independently reviewable The repository should be in a working state after each commit References [Sentry Commit Messages](https://develop.sentry.dev/engineering practices/commit messages/) Limitations Use this skill only when the task clearly matches the scope described above. Direct to main instructions remain subordinate to server side branch protection and required checks. Do not treat the output as a substitute for environment specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.