draft-commit-message-ai-kit

To format a Git commit message with a Jira ticket number and conventional commit type, structure the subject line as `JIRA-NUMBER - type: Brief description`, keeping it under 72 characters. This ensures traceability and aligns with standard conventions.

When drafting Git commit messages, you can use conventional commit types including feat, fix, refactor, perf, docs, ci, build, test, and deps. These types categorize the nature of your staged changes for better project tracking.

To write a multi-line Git commit body using imperative mood, insert a blank line after the subject, then add 1–3 lines starting with action verbs like “Add” instead of “Added.” Use bullet points if documenting multiple staged changes.

Yes, this commit message drafting approach enforces a strict 5-line maximum limit. This includes the `JIRA-NUMBER - type: description` subject line, a blank separator line, and a concise 1–3 line body to keep Git histories readable.

To generate a Netwealth-style commit message for staged Git changes, provide the Jira key, conventional commit type, and change details. The output is a properly formatted message with imperative mood and length constraints applied.

The best way to keep Git commit subjects under 72 characters with a branch-based Jira key is to use the `JIRA-NUMBER - type: Brief description` structure. This format prioritizes the Jira prefix and conventional type while forcing a concise description.