--- name: commit description: 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. risk: critical source: community --- # 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: ```bash 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. 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: ```bash git branch --show-current ``` If still on `main` or `master` (e.g., the user aborted branch creation), stop — do not commit. ## Format ``` ():