git-commits
创建结构良好的git提交。始终在提交时使用此技能——即使是简单的单文件提交。触发器:"commit"、"stage"、"add and commit",或完成任何代码更改后。
📖 中文导读:创建结构良好的git提交。始终在提交时使用此技能——即使是简单的单文件提交。触发器:"commit"、"stage"、"add and commit",或完成任何代码更改后。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: git-commits description: Create well-structured git commits. ALWAYS use this skill when committing - even for simple single-file commits. Triggers: "commit", "stage", "add and commit", or after completing any code changes.
Git Commits
Always invoke this skill for every commit. This ensures consistent, well-structured commits.
Workflow
- Run
git statusandgit diffto see changes - Run
git log --oneline -5to see recent commit style - Determine if changes should be one or multiple commits
- Stage and commit with clear message
When to Split vs Combine
Separate commits:
- CSS vs PHP logic
- Different features (even in same file)
- Refactoring vs new functionality
- Multiple bug fixes (one per fix)
Single commit:
- Related changes for one feature
- A handler + its CSS
- Tests for the feature being added
Commit Message Format
<summary line - what and why, not how>
<optional body with more context>
Examples
Input: Single file change to update details
- $title = __( 'Old title', 'simple-history' );
+ $title = __( 'New title', 'simple-history' );
Output:
Update 5.22.0 update details title
Input: Multiple related changes across files
# file1.php
+ public function new_feature() { ... }
# file2.php
+ add_filter( 'hook', [ $this, 'new_feature' ] );
Output:
Add new feature for X
Register hook and implement handler.
Multiple Repositories
When changes span core + premium:
- Commit core first, then premium
- Use related commit messages