commit

This skill acts as a rigorous gatekeeper for version control operations, ensuring that all code commits align with Sentry’s engineering standards. It is designed for developers and AI agents operating within environments where maintaining a clean, searchable, and issue-linked commit history is mandatory. By intercepting commit requests, the skill prevents direct commits to protected branches like main or master and mandates the use of feature branches, thereby safeguarding repository integrity.

• Automatically enforces conventional commit formatting including type, scope, subject, body, and footer sections.

• Validates branch safety by checking current git status before any commit operation is executed.

• Integrates seamless issue tracking by supporting references like Fixes SENTRY-1234, Fixes #1234, or Refs LINEAR-ABC-123.

• Standardizes commit types such as feat, fix, ref, perf, docs, and chore to ensure consistent metadata categorization.

• Enforces strict grammatical rules for subject lines, requiring imperative mood and present tense without trailing periods.

• Provides automated support for Co-Authored-By attribution when changes are generated by AI assistants like Claude Code, maintaining transparency without verbose conversational clutter.

• Always verify the current branch using git branch --show-current before proceeding with any commit logic.

• If the agent is on a protected branch, utilize the create-branch skill to safely transition to a development context.

• Keep all commit message lines under the 100-character limit to ensure compatibility with standard git viewers and CLI tools.

• Focus the body of the message on the 'what' and 'why' rather than implementation details, providing clear context for future code reviews.

• Do not use non-standard markers like 'Generated by AI' in commit messages; adhere strictly to the requested Co-Authored-By footer format.

• Use this skill whenever interacting with git workflows, including git commit, save changes, or preparing release notes.