commit-prepare

Conventional commit automation analyzes your staged changes and generates formatted commit messages with type, scope, subject, and body following established standards. This ensures consistency in your git history and enables semantic versioning.

Yes, the skill identifies breaking changes in your diff and prompts you to flag them properly in the commit footer, ensuring your commits signal semantic versioning requirements accurately.

Conventional commits follow the pattern: type(scope): subject with a 50-character subject limit in imperative mood, optional 72-character wrapped body, and footers for breaking changes. The skill generates messages adhering to these constraints.

It runs git commands—git status, git diff --cached for staged changes, and git diff for unstaged changes—to examine your modifications, determine commit type and scope, then propose a formatted message via HEREDOC.

No. The skill handles syntax and formatting automatically. You review the proposed message; the skill ensures it meets conventional commits standards without requiring you to memorize format rules.

Manual commits are error-prone and inconsistent; automated conventional commits enforce standards across your team, maintain readable git history, and trigger accurate semantic versioning in automated release pipelines.