git-commit

Stage your changes or leave them in the working tree, then ask the assistant to commit. It runs git diff to analyze the modifications, infers the type and scope, and creates a commit message following the Conventional Commits format.

The supported types are feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. Each type signals the nature of the change, and breaking changes can be marked with an exclamation mark or a BREAKING CHANGE footer.

Yes. The skill stages specific files or patterns with git add before committing, allowing logical grouping of changes. It analyzes git status and diffs to decide which files belong together in one commit.

Yes. The workflow explicitly warns against committing secrets such as .env files, credentials.json, or private keys. It also follows a git safety protocol that forbids destructive commands, force pushes to main, and skipping hooks without explicit request.

If a commit fails due to hooks, the guidance is to fix the underlying issue and create a new commit rather than amending. The skill never skips hooks with --no-verify unless the user explicitly asks.