Generating Commit Messages

Generate commit messages automatically by analyzing your git diff --staged output. The Skill examines staged changes and produces a conventional commit message with a type (feat, fix, refactor, test, docs, chore), an imperative summary under 50 characters, and optional body and footer sections that follow git best practices.

Conventional Commit format structures messages with a type prefix (feat, fix, refactor, test, docs, chore), a concise imperative summary, and optional body and footer. This standardized format makes your git log readable, enables automated changelog generation, and simplifies collaboration across teams.

Yes. Invoke the Skill with the --commit flag to analyze git status and staged diffs, generate a conventional commit message, and auto-create the commit without manual confirmation, streamlining your workflow after completing tasks or TDD cycles.

Use this Skill after staging code changes, completing a feature, or achieving a green test state in TDD. It ensures consistent, informative commit messages that maintain a clear project history without manual writing effort.

Yes. The Skill enforces Conventional Commit Format with an imperative summary capped at 50 characters, aligning with git best practices for conciseness and clarity in log readability.

The Skill analyzes your git diff --staged to generate relevant messages. For complex changes, it supports an optional body section beyond the 50-character summary, allowing detailed explanation while keeping the headline concise.