Conventional Commits Workflow

Follow these steps to generate a professional git commit message.

Core Mandates

Respect Context: If the project contains a .gitmessage file or the user provides specific instructions, prioritize them. Use assets/gitmessage_template.txt as a reference for formatting.
50/72 Rule: Title must be ≤ 50 characters. Separate body with a blank line. Wrap body lines at 72 characters.
Grammar: Use imperative mood and present tense for the title (e.g., "fix bug", "add feature"). Do not capitalize the first letter and do not use a period at the end.

Read staged changes to determine the nature of the modification.

Short Format: Use for simple, self-explanatory changes. Reference assets/short_template.txt.
Long Format: Use for complex changes or when explicitly requested. Reference assets/long_template.txt.