git-commit

Original：🇨🇳 Chinese

Translated

Use git to commit code in the current repository. This skill is used when the user requests to submit code, write commit messages, execute git commit/push/amend, or mentions terms like submit, commit, push, stage and commit, save changes, create a commit, or when directly specified by a sub-agent.

2installs

Sourcecabinet-fe/prompt-engineering

Added on2026-09-04

NPX Install

npx skill4agent add cabinet-fe/prompt-engineering git-commit

SKILL.md Content (Chinese)

View Translation Comparison →

Git Code Commit

This is an independent tool skill that can be called by any party. The caller specifies when to commit, which files to commit, and key points of the commit message; this skill only handles how to perform the commit.

Objectives

Complete Git commits according to the specified mode. In interactive mode, you can ask whether to push again; in auto mode, only local commits are performed.

Modes

Interactive (default): The user explicitly requests to commit or push.
auto: Specified by the caller. Perform local
```
git add
```
+
```
git commit
```
, push is prohibited, and do not ask whether to push.

Unified Tool Definition

```
Interactive Questioning
```
: A tool built into most Agents, which allows the Agent to ask the user questions and provide options and custom input. Its name may vary across different Agents, such as
```
AskUserQuestion
```
or
```
AskQuestion
```
. Do not use it to ask whether to push in auto mode.

Interactive Mode

Check
```
git status
```
/
```
git diff
```
/
```
git log
```
to understand the intent of the changes.
Determine if the changes contain keys or content that should not be committed, and use the
```
Interactive Questioning
```
tool to confirm with the user.
Organize changes into one or more logical commits; do not include unrelated changes in a single commit.
Write Chinese commit messages in accordance with the Commit Specification.
After confirming safety, execute
```
git add
```
and
```
git commit
```
. Do not use
```
--no-verify
```
.
Use the
```
Interactive Questioning
```
tool to ask whether to push; execute
```
git push
```
only if needed.

Auto Mode

```
git status
```
: If there are no tracked changes and no new files that should be added to the repository → Report "No commits" and end.
If
```
.env
```
, keys, credentials, or files that clearly should not be added to the repository are found → Stop, do not commit, and list them for the user. Do not use questioning to transfer the risk to the user.
Staging scope: If the caller specifies paths, only stage those paths; if not specified, only stage the files that should be added to the repository in this round. Do not include unrelated dirty files. Do not force add paths that are in gitignore.
Create one logical commit; write Chinese messages in accordance with the Commit Specification. If the caller provides key points for the commit message, use them; otherwise, write based on the actual diff.
Execute
```
git add
```
for the specified paths +
```
git commit
```
. Do not use
```
--no-verify
```
. Do not execute
```
git push
```
.
Report the commit hash and indicate that it has not been pushed.

Commit Specification

<Type>(<Scope>)!: <Description>

[Optional Body]

[Optional Footer]

Core Specification

Commit messages must be written in Chinese

Title

Use imperative sentences or concise verb phrases
Describe "what was done", avoid vague descriptions
Try to keep it within 50 characters

Body

Explain why the change was made, not just what was changed
Explain important implementation trade-offs
Mention behavioral changes, compatibility impacts, and migration matters
Try to keep each line within 72 characters

Footer

For breaking changes, use:

破坏性变更: <描述破坏性变更的内容>

Commit Types

Type	Description
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation changes
`style`	Code format changes, no impact on logic
`refactor`	Refactoring, no new features or bug fixes
`perf`	Performance optimization
`test`	Testing-related changes
`build`	Build system or dependency changes
`ci`	CI/CD configuration changes
`chore`	Daily maintenance, miscellaneous tasks
`revert`	Revert a commit