commit

Original：🇨🇳 Chinese

Translated

Perform git commit following Conventional Commits standards

1installs

Sourcemyuon/ccskills

Added on2026-02-14

NPX Install

npx skill4agent add myuon/ccskills commit

SKILL.md Content (Chinese)

View Translation Comparison →

Git Commit (Conventional Commits)

Steps

1. Check the changes with

git status

2. Check for files that should not be committed

Check for the following types of files:

Type	Examples
Secrets	`.env` , `*.pem` , `credentials.json` , `secrets.yaml`
Build artifacts	`node_modules/` , `dist/` , `build/` , `__pycache__/`
IDE settings	`.idea/` , `.vscode/` (if not shared in the project)
OS-generated files	`.DS_Store` , `Thumbs.db`
Logs & caches	`*.log` , `.cache/` , `coverage/`

If there are such files:

Add them to
```
.gitignore
```
Verify they are excluded using
```
git status
```

3. Check differences with

git diff

(optional)

Run this to understand the details of the changes.

4. Create a commit message

Analyze the changes and create a message in Conventional Commits format.

5. Stage changes with

git add .

6. Execute

git commit

(no confirmation needed)

Commit Message Format

Follow Conventional Commits:

<type>[optional scope]: <description>

[optional body]

[optional footer]

Type List

type	Usage
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation-only changes
`style`	Changes that do not affect the meaning of the code (whitespace, formatting, etc.)
`refactor`	Code changes that are neither bug fixes nor feature additions
`perf`	Performance improvement
`test`	Add or modify tests
`chore`	Changes to build processes or tools
`ci`	Changes to CI configurations
`build`	Changes to build system or external dependencies

Scope (Optional)

Indicates the scope of the change. Examples:

```
feat(auth):
```
- Authentication functionality
```
fix(api):
```
- API-related
```
docs(readme):
```
- README

Description

Write in imperative mood (use "add" instead of "added")
Aim for within 50 characters
Do not add a period at the end

Body (Optional)

Write from the 3rd line onwards
The reason or background for the change
Notable implementation details

Examples

feat(models): Add new User model

Implemented the User model as the foundation for user authentication functionality. Passwords are hashed and stored using bcrypt.

fix(api): Fix rate limiting bug

Fixed the issue where request counts per minute were not being calculated correctly. The cause was an incorrect Redis TTL setting.

refactor: Separate authentication middleware

Notes

If there are breaking changes, include
```
BREAKING CHANGE:
```
in the footer
If you updated
```
.gitignore
```
, include that in the commit message