conventional-commit

To fix a rejected git commit message, generate a Conventional Commit in the `type(scope): description` format, using an allowed type like feat or fix, an optional scope, and an imperative description that passes the repo's hook validators.

The correct format for Conventional Commits is `type(scope): description`, requiring one allowed commit type such as feat, fix, or docs, an optional scope, and a concise, imperative description tailored to your repository's validation rules.

To write a Conventional Commit message for an amend or reword workflow, apply the `type(scope): description` pattern using an allowed type, optional scope, and an imperative description to satisfy previously rejected validation checks.

Yes, Conventional Commit generation supports optional body and footer content, allowing you to append details like `BREAKING CHANGE` notes or issue references alongside the required `type(scope): description` pattern.

Yes, you can use Conventional Commits with semantic versioning and repository automation by generating standardized `type(scope): description` messages that hook validators recognize for automated release workflows.

Your git commit is rejected by the validate-commit-msg hook because the message lacks the required Conventional Commits format; you must use the `type(scope): description` pattern with an allowed type to pass validation.