commit

Original：🇺🇸 English

Translated

Stage changes, draft conventional commit messages, and commit with user confirmation. Use when user types /commit, asks to commit changes, or mentions creating a git commit.

2installs

Sourceishakantony/skills

Added on2026-04-30

NPX Install

npx skill4agent add ishakantony/skills commit

SKILL.md Content

View Translation Comparison →

Commit

Quick start

When user triggers

/commit

or asks to commit:

Run
```
git add -A
```
to stage all changes
Run
```
git status
```
and
```
git diff --staged
```
to review changes
Draft a conventional commit message (
```
type(scope): subject
```
)
Present summary + commit message to user
Ask for confirmation via
```
question
```
tool
If confirmed:
```
git commit -m "message"
```

Workflow

1. Stage all changes

Run

git add -A

to stage all modified, added, and deleted files.

2. Review changes

Run in parallel:

```
git status
```
```
git diff --staged
```
```
git log --oneline -5
```
(for context)

Identify:

Modified, added, deleted files
The nature of changes (feature, fix, refactor, docs, test, chore)

3. Draft commit message

Follow Conventional Commits:

feat: new feature
fix: bug fix
docs: documentation changes
style: formatting, missing semicolons, etc.
refactor: code change that neither fixes a bug nor adds a feature
test: adding or correcting tests
chore: build process, dependencies, tooling

Format:

type(scope): subject

Rules:

Subject is lowercase, no trailing period
Max 50 chars for subject line
Include body only if change needs explanation
NEVER mention AI-generated, drafted by AI, or similar

4. Present to user

Show:

## Changes to be committed

<git status output>

## Proposed commit message

<type>(<scope>): <subject>

<type>: <description of why>

5. Ask for confirmation

Use the

question

tool with options:

"Yes, commit" (Recommended)
"Edit message first"
"Cancel"

If user chooses "Edit message first", ask them to provide the new message, then re-present.

6. Execute

On confirmation, run

git commit -m "message"

. If commit fails, show error and offer to fix.

Safety rules

NEVER use
```
git push
```
unless explicitly requested
NEVER use
```
--no-verify
```
or skip hooks unless user asks
NEVER commit
```
.env
```
, credentials, or secrets (warn user if detected)
If working tree is clean, inform user there's nothing to commit