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

Check for package-lock.json (npm), pnpm-lock.yaml (pnpm), yarn.lock (yarn), bun.lockb (bun). Use whichever is present. Default to npm if unclear.

Structured prompt template for generating standardized conventional commit messages. \n \n Provides XML-formatted workflow guiding users through staging changes, inspecting diffs, and constructing commits with type, scope, description, body, and footer fields \n Includes validation rules enforcing Conventional Commits specification compliance, with allowed types (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert) \n Offers six practical examples covering common commit patter

Standardized git commits using Conventional Commits specification with intelligent diff analysis and message generation. \n \n Auto-detects commit type (feat, fix, docs, refactor, perf, test, build, ci, chore, revert) and scope from actual code changes \n Generates semantic commit messages following conventional format with optional body and footer sections \n Intelligently stages files for logical grouping when needed, with support for pattern-based and interactive staging \n Detects breaking c

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.