commit
创建遵循标准前缀(feat, fix, docs, refactor, test, chore等)的原子git提交。阶段变更、审查未提交文件,并生成格式正确的提交信息。在提交代码、创建git提交、阶段文件或用户提及传统提交或提交信息时使用。
📖 中文导读:创建遵循标准前缀(feat, fix, docs, refactor, test, chore等)的原子git提交。阶段变更、审查未提交文件,并生成格式正确的提交信息。在提交代码、创建git提交、阶段文件或用户提及传统提交或提交信息时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: commit description: Creates atomic git commits with conventional commit messages following standard prefixes (feat, fix, docs, refactor, test, chore, etc.). Stages changes, reviews uncommitted files, and generates properly formatted commit messages. Use when committing code, creating git commits, staging files, or when the user mentions conventional commits or commit messages. license: MIT metadata: author: Yves Tkaczyk version: "0.1"
Git Commit Skill
This skill helps you create well-structured, atomic git commits following conventional commit standards.
What this skill does
- Reviews uncommitted changes in your repository
- Stages the appropriate files for commit
- Generates atomic commit messages with conventional commit prefixes
- Ensures commits follow best practices
When to use this skill
Use this skill when you:
- Need to commit changes to your git repository
- Want to create properly formatted commit messages
- Need help determining which files to stage
- Want to follow conventional commit standards
How to use this skill
Review uncommitted changes
- Run
git statusto see what files have been modified - Run
git diff HEADto review the actual changes - Run
git status --porcelainfor a machine-readable status
- Run
Stage the changes
- Add untracked files using
git add - Stage modified files using
git add - Ensure only related changes are staged together for atomic commits
- Add untracked files using
Create the commit message
- Use conventional commit format:
<type>: <description> - Common types include:
feat: A new featurefix: A bug fixdocs: Documentation changesstyle: Code style changes (formatting, missing semicolons, etc.)refactor: Code refactoringtest: Adding or updating testschore: Maintenance tasksperf: Performance improvementsci: CI/CD changesbuild: Build system changes
- Use conventional commit format:
Commit the changes
- Create an atomic commit that represents a single logical change
- Ensure the commit message clearly describes what changed and why
Example
# Review changes
git status
git diff HEAD
# Stage changes
git add src/component.ts
git add tests/component.test.ts
# Commit with conventional message
git commit -m "feat: add new component for user profile display"