Git Commit Stager

Stages atomic changes and writes precise commit messages adhering to the Conventional Commits specification (feat, fix, docs, refactor, test, chore).

1. Purpose

Create clean, bisectable git histories with focused commits.

2. When to Use

Use this skill when:

• Staging and committing code changes after completing a task step.
• Writing structured commit messages (feat(parser): add unicode support).
• Separating unrelated edits into distinct commits.

3. When Not to Use

• Do not use to draft PR descriptions; use github-pr-creator.

4. Required Inputs

• commit_type: feat, fix, docs, refactor, test, chore.
• description: Imperative summary (e.g. add rate limit middleware).

5. Missing-Input Behavior

1. If type is omitted: infer from diff (fix for bug fixes, feat for new functionality, test for test additions).
2. Never commit with vague messages like update or wip.

6. Procedure

Follow these numbered actions:

1. Action 1: Review Staged Diff
   • Execute: git diff --cached (or git status).
2. Action 2: Stage Only Intended Files
   • Execute: git add <files> (avoid git add . if untracked junk exists).
3. Action 3: Format Commit Message
   • <type>(<scope>): <subject>
4. Action 4: Execute Commit
   • Execute: git commit -m "<message>"
5. Action 5: Emit Commit Summary
   • Format per Section 8.

7. Decision Rules

• Commit message subject must be imperative: "add feature", not "added feature".
• If breaking change: append ! after type (feat!: remove v1 auth).

8. Output Format

Emit the report using this template:

### Git Commit Report

- **Commit SHA**: `[hash]`
- **Message**: `[type(scope): subject]`
- **Files Committed**: [Count]

#### Commit Diff Summary
```text
[git log -n 1 --stat output]

## 9. Verification Checklist
- [ ] Commit message follows Conventional Commits.
- [ ] No unwanted files staged (`.env`, `.DS_Store`, build logs).
- [ ] Commit succeeded with exit code 0.

## 10. Common Failures and Recovery
| Failure Symptom | Cause | Recovery Action |
| :--- | :--- | :--- |
| Accidental staging of .env | Ran `git add .` | Run `git reset HEAD .env`. |

## 11. Stop or Escalation Conditions
Stop and ask the user when:
- Git user name or email is not configured in git environment.

## 12. Examples

### Example 1: Successful Execution
**Input:**
```text
Type: fix
Scope: auth
Subject: handle null token in header
Files: src/auth.ts

Output:

### Git Commit Report

- **Commit SHA**: `a1b2c3d`
- **Message**: `fix(auth): handle null token in header`
- **Files Committed**: 1

#### Commit Diff Summary
```text
 src/auth.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

### Example 2: Ambiguous or Missing Input
**Input:**
```text
Commit it.

Output:

### Git Commit Report: Checking Staged Changes

Reviewing `git status` to determine affected files and appropriate Conventional Commit type.

Example 3: Expected Final Output

Output:

### Git Commit Report

- **Commit SHA**: `e4f5a6b`
- **Message**: `test(cart): add zero discount regression test`
- **Files Committed**: 1