git-commit-creator

Conventional commits follow a structured format like `feat(scope): description` that standardizes your Git history. This Skill automates the process by inspecting your changes, generating a properly scoped message, and enforcing branch naming conventions so your commit history remains clean and searchable.

Automated branch naming reduces errors and keeps your workflow uniform. This Skill creates branches with standard prefixes—`feat`, `fix`, `chore`—paired with component names, so every branch follows your project's conventions without manual enforcement.

Yes. This Skill guides you through status checks, staging, and committing in one workflow. It runs `git status` and `git diff` to understand your changes, then handles branch creation and message generation, eliminating repetitive manual steps.

This Skill operates on any Git repository using standard Git commands—status, diff, add, commit, checkout. It enforces conventional commit and branch naming standards, so it fits into existing workflows as long as your team follows or adopts those conventions.

The Skill enforces branch prefixes—`feat`, `fix`, `chore`—with component scopes. If your change doesn't fit these categories, you can still use Git directly; this Skill is optimized for conventional workflows and may not be the best fit for non-standard commit patterns.