git-commit

This Skill generates conventional commit messages by formatting staged changes into standardized types like feature, fix, docs, and chore. It structures the commit header, optional scope, and body to maintain clear version control history.

Conventional commits are a standardized formatting specification for structuring git commit messages to ensure version control consistency. Use them during your development workflow to clearly communicate the nature of changes, such as adding features or fixing bugs.

Yes, you can stage specific files because this Skill provides staging assistance. It guides you to stage only relevant files before committing, promoting atomic commits and discouraging the inclusion of sensitive information in your version control history.

Yes, the git commit generation supports optional scopes and body descriptions. It adheres to the conventional commit specification, allowing you to add context like `feat(auth): implement user login endpoint` along with a detailed body.

The best way to enforce git commit best practices is to use a Skill that promotes atomic commits and guides file staging. This ensures you commit only relevant changes while following the conventional commit format for clear version control history.