Git Commit Workflow

Name: git-commit
Rating: 87
Author: shellicar

Create a commit from staged changes with a concise, single-line message.

Steps

•
Check for staged changes
bash
```
git diff --staged --stat
```
If nothing staged, inform the user.
•
Check for unstaged changes
bash
```
git diff --stat
```
If unstaged changes exist:
- •Show the user WHAT the unstaged changes are (diff content, not just file names)
- •Use AskUserQuestion with options like "Stage them", "Leave unstaged"
- •Stage additional files if requested
•
Read the staged diff content
bash
```
git diff --staged
```
•
Detect convention Run the detection script:
bash
```
~/.claude/skills/git-pr/scripts/detect-convention.sh
```
If it outputs a convention name, load the corresponding <convention>-conventions skill. If it fails, proceed without convention-specific rules.
•
Check branch protection
bash
```
git branch --show-current
```
If on main or master:
- •If convention is shellicar-config → allowed, continue
- •Otherwise → STOP and ask user to create a new branch
Do NOT commit directly to main/master (except for config repos). Offer to create a branch:
bash
```
git checkout -b <branch-name>
```
•
Generate commit message
- •Concise, single line
- •Imperative mood ("Add feature" not "Added feature")
- •No period at end
- •Detail belongs in PRs, not commits
•
Show the user the proposed commit message and ask for confirmation

Use AskUserQuestion with options like "Commit", "Edit message", "Cancel"
•
Commit
bash
```
git commit -m "message"
```
•
Push
bash
```
git push
```

When files are edited, IDE diagnostics may appear. Handle them as follows:

•Errors: Report to the user and address before committing
•Warnings/Information: Ignore silently (e.g., spell-checker warnings)
•Exception: If a warning appears critical or high-severity (e.g., security issue, likely runtime error), you MAY mention it

Do NOT mention trivial non-error diagnostics to the user.

Convention skills may define: