浏览器与自动化
commit
Create well-formatted commits with conventional commit messages and emoji
NeoLabHQ · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add NeoLabHQ/context-engineering-kit --skill commit技能说明
name: commit description: Create well-formatted commits with conventional commit messages and emoji
Claude Command: Commit
Your job is to create well-formatted commits with conventional commit messages and emoji.
Instructions
CRITICAL: Perform the following steps exactly as described:
- Branch check: Checks if current branch is
masterormain. If so, asks the user whether to create a separate branch before committing. If user confirms a new branch is needed, creates one using the pattern<type>/<username>/<description>(e.g.,feature/leovs09/add-new-command) - Unless specified with
--no-verify, automatically runs pre-commit checks likepnpm lintor simular depending on the project language. - Checks which files are staged with
git status - If 0 files are staged, automatically adds all modified and new files with
git add - Performs a
git diffto understand what changes are being committed - Analyzes the diff to determine if multiple distinct logical changes are present
- If multiple distinct changes are detected, suggests breaking the commit into multiple smaller commits
- For each commit (or the single commit if not split), creates a commit message using emoji conventional commit format
Best Practices for Commits
- Verify before committing: Ensure code is linted, builds correctly, and documentation is updated
- Atomic commits: Each commit should contain related changes that serve a single purpose
- Split large changes: If changes touch multiple concerns, split them into separate commits
- Conventional commit format: Use the format
<type>: <description>where type is one of:feat: A new featurefix: A bug fixdocs: Documentation changesstyle: Code style changes (formatting, etc)refactor: Code changes that neither fix bugs nor add featuresperf: Performance improvementstest: Adding or fixing testschore: Changes to the build process, tools, etc.
- Present tense, imperative mood: Write commit messages as commands (e.g., "add feature" not "added feature")
- Concise first line: Keep the first line under 72 characters
- Emoji: Each commit type is paired with an appropriate emoji:
- ✨
feat: New feature - 🐛
fix: Bug fix - 📝
docs: Documentation - 💄
style: Formatting/style - ♻️
refactor: Code refactoring - ⚡️
perf: Performance improvements - ✅
test: Tests - 🔧
chore: Tooling, configuration - 🚀
ci: CI/CD improvements - 🗑️
revert: Reverting changes - 🧪
test: Add a failing test - 🚨
fix: Fix compiler/linter warnings - 🔒️
fix: Fix security issues - 👥
chore: Add or update contributors - 🚚
refactor: Move or rename resources - 🏗️
refactor: Make architectural changes - 🔀
chore: Merge branches - 📦️
chore: Add or update compiled files or packages - ➕
chore: Add a dependency - ➖
chore: Remove a dependency - 🌱
chore: Add or update seed files - 🧑💻
chore: Improve developer experience - 🧵
feat: Add or update code related to multithreading or concurrency - 🔍️
feat: Improve SEO - 🏷️
feat: Add or update types - 💬
feat: Add or update text and literals - 🌐
feat: Internationalization and localization - 👔
feat: Add or update business logic - 📱
feat: Work on responsive design - 🚸
feat: Improve user experience / usability - 🩹
fix: Simple fix for a non-critical issue - 🥅
fix: Catch errors - 👽️
fix: Update code due to external API changes - 🔥
fix: Remove code or files - 🎨
style: Improve structure/format of the code - 🚑️
fix: Critical hotfix - 🎉
chore: Begin a project - 🔖
chore: Release/Version tags - 🚧
wip: Work in progress - 💚
fix: Fix CI build - 📌
chore: Pin dependencies to specific versions - 👷
ci: Add or update CI build system - 📈
feat: Add or update analytics or tracking code - ✏️
fix: Fix typos - ⏪️
revert: Revert changes - 📄
chore: Add or update license - 💥
feat: Introduce breaking changes - 🍱
assets: Add or update assets - ♿️
feat: Improve accessibility - 💡
docs: Add or update comments in source code - 🗃️
db: Perform database related changes - 🔊
feat: Add or update logs - 🔇
fix: Remove logs - 🤡
test: Mock things - 🥚
feat: Add or update an easter egg - 🙈
chore: Add or update .gitignore file - 📸
test: Add or update snapshots - ⚗️
experiment: Perform experiments - 🚩
feat: Add, update, or remove feature flags - 💫
ui: Add or update animations and transitions - ⚰️
refactor: Remove dead code - 🦺
feat: Add or update code related to validation - ✈️
feat: Improve offline support
- ✨
Guidelines for Splitting Commits
When analyzing the diff, consider splitting commits based on these criteria:
- Different concerns: Changes to unrelated parts of the codebase
- Different types of changes: Mixing features, fixes, refactoring, etc.
- File patterns: Changes to different types of files (e.g., source code vs documentation)
- Logical grouping: Changes that would be easier to understand or review separately
- Size: Very large changes that would be clearer if broken down
Examples
Good commit messages:
- ✨ feat: add user authentication system
- 🐛 fix: resolve memory leak in rendering process
- 📝 docs: update API documentation with new endpoints
- ♻️ refactor: simplify error handling logic in parser
- 🚨 fix: resolve linter warnings in component files
- 🧑💻 chore: improve developer tooling setup process
- 👔 feat: implement business logic for transaction validation
- 🩹 fix: address minor styling inconsistency in header
- 🚑️ fix: patch critical security vulnerability in auth flow
- 🎨 style: reorganize component structure for better readability
- 🔥 fix: remove deprecated legacy code
- 🦺 feat: add input validation for user registration form
- 💚 fix: resolve failing CI pipe