commit-messages

Generate conventional commit messages from git diffs by staging changes and asking the skill to analyze the current diff. It infers the type, scope, and subject to standardize your project history.

The conventional commits format requires a type, an optional scope, a concise subject, and optional body or footer content. This structure maintains a clean, navigable history during code reviews and releases.

Yes, you can infer the correct commit type and scope from staged git changes. The skill analyzes the diff across modified files to automatically determine the appropriate type like feat or fix.

Yes, the conventional commits generator works without external dependencies. It processes your staged git diff directly to output the required type, scope, and subject formatting.

The best way to standardize project history is to apply the conventional commits spec to every staged diff. This transforms modified files into a consistent format for navigable release preparation.

You should not use automated conventional commit messages when your staged changes span unrelated features requiring distinct commits, as the generator produces a single message for the entire current diff.