create-commit-message

To generate a conventional commit message from staged git changes, the Skill analyzes your current diff to infer the change type and scope, then produces a concise subject line under 72 characters with an optional explanatory body.

Yes, the commit message generation respects existing project conventions by detecting and adjusting to commitlint or config files when present, ensuring the output matches your established formatting rules.

Conventional commit automation infers the change type and scope by evaluating the staged diff content, identifying the affected files and logic, and mapping those changes to standard conventional commit categories.

The maximum length for the subject line in an auto-generated conventional commit is 72 characters, ensuring compliance with standard git formatting guidelines while maintaining conciseness.

Yes, you can automatically add an explanatory body to your conventional commit message; the Skill generates an optional body explaining the rationale behind the staged changes.

Your generated commit message format may not match project conventions if commitlint or specific config files are not present in your environment, causing the tool to fall back to default conventional commit standards.