commit

Original：🇺🇸 English

Translated

Read this skill before making git commits

2installs

Added on2026-02-18

NPX Install

npx skill4agent add mitsuhiko/agent-stuff commit

Create a git commit for the current changes using a concise Conventional Commits-style subject.

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

Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (no
```
Signed-off-by
```
).
Only commit; do NOT push.
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review
```
git status
```
and
```
git diff
```
to understand the current changes (limit to argument-specified files if provided).
(Optional) Run
```
git log -n 50 --pretty=format:%s
```
to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Stage only the intended files (all changes if no files specified).
Run
```
git commit -m "<subject>"
```
(and
```
-m "<body>"
```
if needed).