commit▌

Structured commit message format following the Conventional Commits specification. \n \n Defines 12 commit types (feat, fix, refactor, docs, test, chore, ci, build, perf, style, deps, revert) with clear purposes and semantic versioning correlation \n Enforces a required header format with optional scope and body, all lines under 100 characters, subject line capped at 70 characters \n Includes guidelines for imperative present-tense language, body content explaining what and why, and support for

You are tasked with creating git commits for the changes made during this session.

Enforces Sentry conventional commit format with proper types, scopes, and issue references. \n \n Requires feature branch creation before committing to main or master; uses the create-branch skill to manage branch workflow \n Supports 12 commit types (feat, fix, ref, perf, docs, test, build, ci, chore, style, meta, license) with clear subject line rules and footer patterns for issue references \n Includes Co-Authored-By attribution for AI-generated changes and handles breaking changes with expli

Create logical, well-described git commits with staged review and Conventional Commits formatting. \n \n Guides you through inspecting changes, deciding commit boundaries, and staging only intended modifications using patch mode when needed \n Enforces Conventional Commits format (type, scope, subject, body, footer) with clear separation of what changed and why \n Includes a pre-commit checklist covering secrets detection, accidental debug code, and unrelated formatting to catch issues before sh

Load with: base.md

Follow these conventions when creating commits for Sentry projects.

A skill for creating properly formatted Git commit messages following the Conventional Commits specification.

Analyze staged changes and generate commit message:

Follow these conventions when creating commits for Sentry projects.

Type and scope are examples only; adjust to fit the repo and changes.