conventional▌

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

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