git-commit-helper

Conventional commit messages require analyzing staged git diffs to extract the semantic meaning of changes. The tool parses diff data and outputs structured messages formatted as type(scope): description, covering common types like feat, fix, docs, refactor, or chore.

The conventional commits format is a structured message specification using type(scope): description to standardize code changes. You should use it during code reviews and release notes generation to provide clear, structured summaries of staged changes across your codebase.

Yes, you can analyze staged changes across different codebases to suggest commit messages. The tool works across codebases by requiring access to the diff data of the changes, producing precise, well-structured summaries aligned with the conventional commits specification.

Yes, the commit message generator supports common types including feat, fix, docs, style, refactor, test, and chore. It also supports optional scopes within the conventional commits format to improve clarity and provide better context for the changes.

The best way to automate commit message creation is to use a diff analysis tool that enforces the conventional commits format. By feeding the staged git diff data directly into the tool, you get a precise, well-structured summary of the changes automatically.

You need to provide diff data because the commit message generator requires access to the actual code changes to produce a precise summary. Without analyzing the git diffs, the tool cannot accurately determine the correct type, scope, and description for the commit.