conventional-committer

Original：🇨🇳 Chinese

Translated

Stage changes and generate commit messages that comply with the Conventional Commits specification.

1installs

Added on2026-02-07

NPX Install

npx skill4agent add caomeiyouren/momei conventional-committer

Staging: Add modified files to the git staging area.
Message Generation: Create commit messages that follow the
```
type(scope): description
```
format (e.g.,
```
feat(auth): add login page
```
).
Committing: Execute
```
git commit
```
.

Specification Alignment: Before committing, confirm compliance with Development Standards - Commit Scale & Atomic Changes.
Scale Check: Mandatorily check the number of files changed. In principle, the number of files should not exceed 10; the corresponding feature point must be single-purpose.
Task Association: Each commit should be associated with exactly one atomic item in Todo.
Pre-commit Check: Before performing any git commit operation, confirm that
```
@code-auditor
```
has passed
```
pnpm typecheck
```
,
```
pnpm lint
```
and necessary targeted tests.
Status Verification: Check
```
git status
```
to see which content needs to be staged.
Message Generation: Analyze the changes to determine the
```
type
```
(feat, fix, docs, style, refactor, test, perf, build, ci, chore, revert),
```
scope
```
(optional, e.g., component name, module) and
```
description
```
. The message description must use Chinese uniformly.
Commit: Run
```
git commit -m "..."
```
.
Verification: Ensure the message complies with
```
commitlint.config.ts
```
.

Input: "Commit the new user profile feature." Action:

git add .

, analyze changes, generate message

feat(user): Implement user profile page with avatar upload functionality

git commit

Staging: Add modified files to the git staging area.
Message Generation: Create commit messages that follow the
```
type(scope): description
```
format (e.g.,
```
feat(auth): add login page
```
).
Committing: Execute
```
git commit
```
.

Specification Alignment: Before committing, confirm compliance with Development Standards - Commit Scale & Atomic Changes.
Scale Check: Mandatorily check the number of files changed. In principle, the number of files should not exceed 10; the corresponding feature point must be single-purpose.
Task Association: Each commit should be associated with exactly one atomic item in Todo.
Pre-commit Check: Before performing any git commit operation, confirm that
```
@code-auditor
```
has passed
```
pnpm typecheck
```
,
```
pnpm lint
```
and necessary targeted tests.
Status Verification: Check
```
git status
```
to see which content needs to be staged.
Message Generation: Analyze the changes to determine the
```
type
```
(feat, fix, docs, style, refactor, test, perf, build, ci, chore, revert),
```
scope
```
(optional, e.g., component name, module) and
```
description
```
. The message description must use Chinese uniformly.
Commit: Run
```
git commit -m "..."
```
.
Verification: Ensure the message complies with
```
commitlint.config.ts
```
.

Input: "Commit the new user profile feature." Action:

git add .

, analyze changes, generate message

feat(user): Implement user profile page with avatar upload functionality

git commit