commit

Original：🇺🇸 English

Translated

1 scriptsChecked / no sensitive code detected

Create and execute Git commits in Conventional Commits format with a required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.

1installs

Sourcebohdan-shulha/skills

Added on2026-02-22

NPX Install

npx skill4agent add bohdan-shulha/skills commit

SKILL.md Content

View Translation Comparison →

Commit

Overview

Create safe, structured commits with deterministic checks and consistent message quality. Run a guard before staging, then commit using Conventional Commits with a descriptive subject and required body bullets.

Workflow

Run safety guard:
- ```
python3 scripts/precommit_guard.py
```
Abort immediately if the guard exits non-zero.
- Do not run
```
git add
```
  or
```
git commit
```
  when blocked.
Stage all changes only after guard passes:
- ```
git add . -A
```

Review staged changes:

```
git diff --cached --name-only
```
```
git diff --cached --stat
```

Compose commit subject and body using the format rules below.
Execute commit:
- ```
git commit -m "<subject>" -m "<body>"
```

Safety Guard Rules

Abort when any path matches one of these conditions:

Log-like files:

```
*.log
```
,
```
*.out
```
,
```
*.err
```

npm-debug.log*

,

yarn-debug.log*

,

yarn-error.log*

,

pnpm-debug.log*

any file under a
```
logs/
```
directory

Untracked high-risk binary extensions:

```
.exe
```
,
```
.dll
```
,
```
.so
```
,
```
.dylib
```
,
```
.bin
```
,
```
.class
```
```
.zip
```
,
```
.tar
```
,
```
.gz
```
,
```
.bz2
```
,
```
.xz
```
,
```
.7z
```
,
```
.rar
```
,
```
.jar
```
```
.iso
```
,
```
.dmg
```
,
```
.db
```
,
```
.sqlite
```
,
```
.sqlite3
```

If blocked, list offending files grouped by reason and request user action. Do not auto-delete files.

Commit Message Format

Use Conventional Commits subject:

```
<type>(<scope>): <description>
```
Scope is optional, but prefer it when clear.
Subject must describe what changed (not only intent), be imperative, and avoid trailing period.
Keep subject concise (prefer <= 72 chars).

Allowed

type

values:

feat

,

fix

,

refactor

,

docs

,

test

,

chore

,

build

,

ci

,

perf

,

style

,

revert

Require commit body:

Provide bullet lines summarizing key changes and impact.
Mention migration/risk notes when relevant.
Use concise, factual bullets.

Example:

Subject:

fix(auth): handle token refresh race in session middleware

Body:

- Serialize refresh attempts per user session to prevent duplicate refresh calls.

- Add timeout handling so failed refresh does not block subsequent requests.

- Update session middleware tests for concurrent request scenarios.

Execution Notes

Prefer one logical commit for the current request.
If changes are unrelated, split into separate commits and repeat the guard + staging flow for each.
If message quality is uncertain, summarize staged diff first, then derive subject/body.