{"id":"c9888829-70a5-40f7-b7ff-d7e044d3e62f","shortId":"6Qks7b","kind":"skill","title":"commit","tagline":"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.","description":"# Sentry Commit Messages\n\nFollow these conventions when creating commits for Sentry projects.\n\n## When to Use\n- The user asks to commit code, prepare a commit message, or save changes in git.\n- You need Sentry-style commit formatting with conventional commit structure and issue references.\n- The task requires enforcing branch safety before committing, especially avoiding direct commits on `main` or `master`.\n\n## Prerequisites\n\nBefore committing, always check the current branch:\n\n```bash\ngit branch --show-current\n```\n\n**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.\n\nUse the `create-branch` skill to create the branch. After `create-branch` completes, verify the current branch has changed before proceeding:\n\n```bash\ngit branch --show-current\n```\n\nIf still on `main` or `master` (e.g., the user aborted branch creation), stop — do not commit.\n\n## Format\n\n```\n(): \n\n\n\n