|
|
|
@ -27,17 +27,18 @@ Make a git commit, distinguishing between user and AI contributions. |
|
|
|
|
|
|
|
|
|
|
|
2. **Check for commit message** |
|
|
|
2. **Check for commit message** |
|
|
|
|
|
|
|
|
|
|
|
**Capitalization rule**: Commit messages should start with a capital letter, |
|
|
|
**Commit message formatting rule**: Commit messages should start with a |
|
|
|
unless it refers to a tool or project that explicitly uses lowercase as its |
|
|
|
capital letter, unless it refers to a tool or project that explicitly uses |
|
|
|
name (e.g., "go", "npm", "rustc"). |
|
|
|
lowercase as its name (e.g., "go", "npm", "rustc"). They must adhere to the |
|
|
|
|
|
|
|
72-character wide title plus (optional) description convention. |
|
|
|
|
|
|
|
|
|
|
|
If the user did NOT provide a commit message, generate one from staged changes: |
|
|
|
If the user did NOT provide a commit message, generate one from staged changes: |
|
|
|
```bash |
|
|
|
```bash |
|
|
|
git diff --staged --stat |
|
|
|
git --no-pager diff --staged |
|
|
|
``` |
|
|
|
``` |
|
|
|
Create a reasonable commit message based on the changes. |
|
|
|
Create a reasonable commit message based on the changes. |
|
|
|
|
|
|
|
|
|
|
|
If thed user DID provide a message, format it into a proper commit message. |
|
|
|
If the user **DID** provide a message, format it into a proper commit message. |
|
|
|
|
|
|
|
|
|
|
|
3. **Show commit message and confirm** |
|
|
|
3. **Show commit message and confirm** |
|
|
|
|
|
|
|
|
|
|
|
|