git-commit

Original：🇺🇸 English

Not Translated

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

3installs

Sourceclubmediterranee/ai-core

Added on2026-04-30

NPX Install

npx skill4agent add clubmediterranee/ai-core git-commit

SKILL.md Content

Git Commit with Conventional Commits

Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.

Conventional Commit Format

<type>(optional scope): <description>

[optional body]

[optional footer(s)]

Breaking Changes

# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting/style (no logic)
`refactor`	Code refactor (no feature/fix)
`perf`	Performance improvement
`test`	Add/update tests
`build`	Build system/dependencies
`ci`	CI/config changes
`chore`	Maintenance/misc
`revert`	Revert commit

Workflow

1. Analyze Diff

bash

# Check status first
git status --porcelain

# If nothing to commit, stop and inform the user
# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

bash

# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p

Never commit secrets (.env, credentials.json, private keys).

3. Generate Commit Message

Analyze the diff to determine:

Type: What kind of change is this?
Scope: What area/module is affected?
Description: One-line summary of what changed (present tense, imperative mood, <72 chars)

4. Execute Commit

bash

# Single line
git commit -m "<type>(scope): <description>"

# Multi-line with body/footer
git commit -m "<type>(scope): <description>" \
  -m "<optional body>" \
  -m "<optional footer>"

5. Output

After a successful commit, display:

✔ <type>(scope): <description>
  commit <short-hash>

If the commit fails (hook rejection), report the hook output and stop — do not retry or amend.

Best Practices

Write commit messages in English
One logical change per commit
Present tense: "add" not "added"
Imperative mood: "fix bug" not "fixes bug"
Keep description under 72 characters
Reference issues when applicable:
```
Closes #123
```
,
```
Refs #456
```

Git Safety Protocol

NEVER update git config
NEVER run destructive commands (--force, hard reset) without explicit request
NEVER skip hooks (--no-verify) unless user asks
NEVER force push to main/master
NEVER add
```
Co-Authored-By
```
trailers (e.g.
```
Co-Authored-By: Claude ...
```
). Commits must always appear under the developer's name only
If commit fails due to hooks, fix and create NEW commit (don't amend)