git-commit

Conventional Commits enforce a standard format—type(scope): subject—across all repository changes. This format makes commit history readable, enables automation, and helps teams quickly understand what changed and why. Use this Skill to generate compliant messages like `feat(auth): add OAuth2 login flow` for every commit.

Conventional Commits is a specification that structures commit messages as type(scope): subject with optional body. It clarifies whether changes are features, fixes, refactors, or docs, making version control history searchable and enabling tools to automate changelog generation and semantic versioning.

When staging files across multiple areas, include a body in your commit message to explain the broader context and impact. This Skill suggests including a body for multi-file changes and guides you to structure it meaningfully, ensuring downstream reviewers understand the full scope of your changes.

Common types include feat (feature), fix (bug fix), refactor, docs, and deploy. Scopes identify the affected area—ui, auth, api, database—specific to your project. This Skill provides examples and helps you choose the right combination based on your staged changes and repository context.

This Skill enforces Conventional Commits format by inspecting staged files and guiding you to structure each message correctly. While this Skill provides real-time guidance, teams often pair it with pre-commit hooks or CI checks to block non-compliant messages before they reach version control.

Include a body when changes span multiple files, affect significant functionality, or need context beyond the subject line. This Skill automatically suggests a body for multi-file commits and explains when substantial changes warrant detailed explanation to help future maintainers understand the reasoning behind the change.