Commit Command

Create a commit with a well-formatted message based on the actual file changes.

Arguments

• No flag: Stage all modified/new files before committing
• -s or --staged: Use only files already staged

Process

1. Gather context (run in parallel):

   git status
   git diff HEAD
   git log --oneline -5
   

2. Analyze changes:

   • Review the diff output to understand what changed
   • Base your analysis solely on the file contents, not conversation context
   • Determine the appropriate commit type

3. Stage files (if not using -s/--staged):

   git add .
   

4. Create commit using HEREDOC format:

   git commit -m "$(cat <<'EOF'
   type: concise description
   
   - Optional body item 1
   - Optional body item 2
   EOF
   )"
   

5. Verify commit:

   git log -1 --format="%B"
   git status
   

6. Handle pre-commit hooks (if files were modified):

   • Check authorship: git log -1 --format='%an %ae'
   • If safe, amend the commit with modified files (one retry only)

Commit Types

Message Format

type: concise description in imperative mood

- Optional: area or component affected
- Optional: another key change

Guidelines

• Analyze the actual diff, not the conversation context
• Message should reflect the current state of the implementation
• Be specific about functionality, not generic
• Focus on WHAT is being done, not HOW
• Use imperative mood: "add", "fix", "implement"
• Do not mention specific files or technical decisions
• Do not reference future tasks or architectural reasoning
• Do not mention specific package versions (e.g., "update lodash to 4.17.21" -> "update lodash")
• Include a body only when the change spans 3+ functional areas (keep to 3-4 concise list items)

Task

Create a commit for changes with $ARGUMENTS.

Use only git commands. Do not use other tools or send additional messages beyond the tool calls.