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:

git branch --show-current

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.