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.
The commit skill standardizes and safeguards the process of creating Git commits for Sentry projects by enforcing structured commit message conventions and repository hygiene rules. It ensures that all commits follow a consistent conventional commit format, include appropriate issue references, and adhere to formatting constraints such as subject length and line width limits. The skill also prevents unsafe workflows by requiring verification of the current Git branch before committing. If a user is working directly on the main or master branch, the skill automatically requires creation of a feature branch unless the user explicitly requests otherwise. This helps reduce accidental direct commits to protected branches and improves repository management consistency.
The skill provides detailed guidance for constructing commit messages, including supported commit types, subject line conventions, body formatting requirements, and footer issue references. It emphasizes writing clear commit messages that explain what changed and why, while avoiding unnecessary implementation details. The skill also includes safeguards against exposing sensitive information such as customer data, emails, support ticket contents, or personally identifiable information in commit history. In addition, it defines proper command-line commit practices to avoid malformed multiline commit messages and supports attribution requirements for AI-generated changes through standardized Co-Authored-By footers.
This skill is designed for developers, engineering teams, and AI coding agents working in repositories that require strict commit discipline and traceable issue management. It is especially useful in collaborative environments where commit consistency, automated issue linking, and branch safety policies are important. Teams using GitHub issues, Sentry issue tracking, or Linear workflows can use the skill to maintain clean project history and improve collaboration across code reviews, releases, and automated tooling.
This skill should be used whenever creating Git commits, including tasks involving commit messages, saving code changes, or running git commit commands.
The skill requires creating a feature branch before committing unless the user explicitly requests committing directly to the main or master branch.
The skill supports conventional commit formats with types such as feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, and license.
Yes. The skill supports footer references using patterns such as Fixes GH-1234, Fixes #1234, Fixes SENTRY-1234, and Refs LINEAR-ABC-123.
Yes. Commit messages must avoid customer data, personally identifiable information, support ticket contents, and improperly escaped newline sequences in CLI commit commands.
Quick Setup:
.claude/skills/Repository
getsentry/skills