conventional-committer

Conventional Committer Skill

• Staging: Add modified files to the git staging area.
• Message Generation: Create a commit message following the type(scope): description format (e.g.: feat(auth): add login page)。
• Committing: Execute git commit。

Instructions

1. Worktree Awareness: Before committing, confirm the current directory (e.g. ../momei-dev), ensuring the commit is made in the correct branch and context.
2. Specification Alignment: Before committing, it must be confirmed that the development specification。
3. Scale Verification: Mandatory check of the number of files changed in this change. In principle, the number of files must not exceed 10; the corresponding feature point must be single.
4. Task Association: Each commit should and only should be associated with Todo one atomic item.
5. Pre-commit Check: Before performing any git commit operation, confirm that @code-auditor has passed pnpm typecheck, pnpm lint and the necessarytargeted tests。
6. Verify Status: Check git status to see what needs to be staged.
7. Generate Message: 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 uniformly usesChinese。
8. Commit: Run git commit -m "..."。
9. Verify: Ensure the message conforms to commitlint.config.ts。

Usage Example

Input: "Commit the new user profile feature." Action: git add ., analyze the changes, generate the message feat(user): 实现带有头像上传功能的用户个人资料页面, git commit。