commit-helper

Conventional commit messages follow a structured format (type, scope, description) that automates commit generation by analyzing your staged Git changes. This skill examines what you've modified and suggests a properly formatted message like `feat(classes): add Recipe class`, ensuring consistency and readability across your project history.

A conventional commit is a standardized format specifying type (feat, fix, docs, style, refactor, perf, test, chore) and scope to create machine-readable, semantic commit history. It enables automated changelog generation, clearer code review, and project standards enforcement without manual formatting overhead.

Yes, commit validation checks format correctness, verifies type and scope against convention rules, enforces description length under 72 characters, and prevents common mistakes. It catches structural problems before commits are recorded, maintaining clean version control history.

After the initial description line, conventional commits support an optional body explaining rationale and references, plus a footer documenting breaking changes. This skill generates all sections from your staged changes, creating complete commit messages with context for future developers.

The skill handles scoped changes across templates, classes, properties, docs, CI workflows, and build scripts, supporting new features, bug fixes, documentation updates, style changes, refactors, performance improvements, tests, and breaking changes in a single conventional format.

Basic familiarity with staged Git changes helps, but the skill automates the convention rules—you stage changes and it generates the formatted message. No deep version control expertise required; the skill handles format enforcement and validation automatically.