commit-workflow

Original：🇺🇸 English

Translated

Create safe Conventional Commit messages and commits from current working tree changes.

1installs

Added on2026-02-15

NPX Install

npx skill4agent add samuerio/.dotfiles commit-workflow

Use this skill when the user asks to create a commit from current repository changes.

Create exactly one local git commit that includes only intended files and uses a concise Conventional Commits-style subject. Do not push.

<type>(<scope>): <summary>

Body is optional. If needed, insert a blank line after the subject.
Do not add breaking-change markers/footers.
Do not add sign-offs.
Commit only. Never push.
If file inclusion is ambiguous, ask the user which files to include before committing.
Never include likely secrets (
```
.env
```
, key files, credentials) unless user explicitly requests it.

Inspect repository state:
- ```
git status
```
- ```
git diff
```
- ```
git diff --staged
```
Optionally inspect recent subject style:
- ```
git log -n 50 --pretty=format:%s
```
Decide the file set to commit:
- If unambiguous, proceed.
- If ambiguous, ask user which files to include.
Stage only intended files.
Draft a concise subject reflecting why the change exists.
Create one commit.
Verify final state with
```
git status
```
and report:
- commit hash
- subject
- staged/unstaged leftovers (if any)

If commit fails due to hooks, inspect hook output and fix the issue.
After fixing, create a new commit (do not amend unless user asked to amend).
If there are no changes to commit, report that clearly and do not create an empty commit.

bash

git status
git diff
git diff --staged
git log -n 50 --pretty=format:%s
git add <paths>
git commit -m "<type>(<scope>): <summary>"
git status