git-commit-writer

To generate conventional commit messages from a diff, input your staged changes or file diffs. The skill derives a standardized message that conforms to Conventional Commits 1.0.0, outputting a complete subject line, optional body, and optional footer.

A conventional commit message standardizes version control history by enforcing a specific structure. It applies a proper type, optional scope, and subject length to code changes, ensuring repository logs remain consistent and machine-readable across feature branches or hotfixes.

Yes, you can use staged changes to create a commit message. The generator validates the type and optional scope according to the Conventional Commits specification, ensuring your staged changes produce a correctly formatted and standardized commit subject line.

The best way to enforce commit message subject length and body rules is to derive commits from diffs automatically. This approach validates type, subject length, and the inclusion of body and footers according to the spec, removing human error from the process.

No, you do not need to manually format the footer. When generating commits from code diffs, the skill automatically handles the inclusion and formatting of optional footers according to the Conventional Commits 1.0.0 specification rules.