commit-message

To generate a conventional commit message, the skill analyzes your staged Git changes and recent commit history, then crafts a structured message with type, scope, subject, and body. It reviews git status and git diff to ensure factual and readable output.

The Conventional Commits specification structures Git messages using a defined format of type, scope, subject, and body. This skill applies that specification by analyzing your code modifications and generating imperative subjects that clearly describe the modifications.

Yes, you can automatically analyze git diff to write an imperative commit subject. The skill reviews staged and unstaged diffs alongside recent logs to generate factual, readable messages adhering to version control best practices.

This commit message generator integrates with your existing version control workflow by running standard git commands like status, diff, and log. It requires no external dependencies to analyze changes and suggest structured messages.

The best way to write informative Git commit bodies for code review is to automate analysis of your current changes. The skill evaluates diffs and recent logs to produce structured, factual messages that improve readability for collaborators.

Git commit messages often lack context when recent repository history is ignored. This skill reviews your last three commits using git log to understand conventions and generate a structured message that fits your project's version history.