git-commit-message

To generate a git commit message automatically, the Skill analyzes your `git diff --cached` output to determine the appropriate type and scope, then produces a single conformant header and body based on the detected staged changes.

Werf commit message conventions require a specific format encompassing a header with a type and scope, strict header length limits, and subject and body rules as outlined in the project's CONTRIBUTING.md#conventions file.

You can enforce consistent git commit conventions by using this Skill to automatically generate standardized Werf-style commit messages from staged changes, which standardizes project history and improves the code review process.

Yes, the commit message generator works without external dependencies, requiring only your staged git changes to analyze the diff and output a properly formatted Werf-style commit message header and body.

The best way to write a Werf-style commit subject and body is to analyze the staged diff to determine the correct type and scope, then apply the length limits and formatting guidelines defined in CONTRIBUTING.md#conventions.

A generated commit message may not match the expected Werf format if the staged changes are ambiguous, making it difficult to determine the correct type and scope required by the Werf conventions and subject rules.