git-commit-helper

Conventional Commits is a specification for clear, standardized commit messages with a structured format: type(scope): description. This Skill analyzes your git diffs and suggests the appropriate type, scope, and imperative-mood description under 50 characters, plus an optional body explaining the motivation behind changes.

Yes. This Skill analyzes diffs to identify logically separate changes and guides you in splitting large commits into atomic, well-documented commits. Each receives a properly formatted Conventional Commits message explaining its specific purpose.

Commit messages should convey motivation, not just code changes. This Skill produces messages with a concise summary line and generates optional body content that documents the reasoning, context, and impact—helping future readers understand the decision behind the code.

Yes. This Skill detects breaking changes in your diffs and generates Conventional Commits messages that properly flag them, ensuring your team is notified of incompatible API or behavior changes through standardized commit format indicators.

Staged changes are ready to commit; unstaged changes are still in progress. This Skill analyzes both to generate appropriate commit messages, letting you review staged changes for immediate commitment or work through unstaged changes before staging them for a commit.

Conventional Commits provides a standardized format for all commit messages, improving readability and tooling integration. This Skill generates compliant messages automatically by analyzing diffs and applying consistent type, scope, and description rules your team can adopt as workflow standard.