git_commit_helper

Git Commit Helper

When to Use This Skill

Activate this skill when the user:

• Explicitly asks to "commit" their changes
• Says "save my work" or "save these changes"
• Says "create a commit" or "make a commit"
• Asks you to commit after completing implementation work
• Mentions they want to save progress to git

Core Process

Step 1: Analyze Current State

Run these commands in parallel to understand the changes:

git status                    # See all changed files
git diff                      # View modifications
git diff --staged            # View staged changes
git log --oneline -n 5       # Check recent commit style

Step 2: Plan Your Commits

Think about:

• What changed: Review the conversation history to understand what was accomplished
• Logical grouping: Which files belong together?
• Clear messages: Draft descriptive commit messages in imperative mood
• Why over what: Focus on the purpose of changes, not just the mechanics

Consider whether changes should be:

• One commit: If all changes are part of a single logical unit
• Multiple commits: If there are distinct, separable changes (e.g., refactoring + new feature)

Step 3: Present Your Plan

Show the user a clear plan before executing:

I plan to create [N] commit(s) with these changes:

Commit 1:
Files: [list specific files]
Message: [proposed commit message in imperative mood]

[Commit 2, 3, etc. if multiple...]

Shall I proceed?

Important:

• Be specific about which files go in each commit
• Show the complete commit message you'll use
• Wait for user confirmation

Step 4: Execute Upon Confirmation

Once the user approves:

# Add specific files (NEVER use -A or .)
git add path/to/file1.js path/to/file2.ts

# Create commit with planned message
git commit -m "Your planned message here"

# Show the result
git log --oneline -n [number of commits you created]

Never use:

• git add -A
• git add .
• git commit -a