commit

Commit Skill

Creates well-formatted commits following conventional commit standards.

When to Use

• User says "commit", "commit these changes", or uses /commit
• After code changes are ready to be committed
• Need help with commit message formatting
• Want automatic detection of multi-concern changes

Core Features

• GPG signing with cached passphrase (if $GPG_PASSPHRASE set)
• Staged vs unstaged detection - commits only staged files when present
• Split suggestions - analyzes diffs for multiple logical changes
• Conventional commits - <type>: <description> format
• Pre-commit hook integration - respects Husky/other hooks
• Always --signoff - DCO compliance

---

Context

• Current git status: !git status
• Current git diff (staged and unstaged): !git diff HEAD
• Current branch: !git branch --show-current
• Recent commits: !git log --oneline -10

---

Process

⚠️ CRITICAL: ALWAYS start with Step 1 (Environment Check) before attempting any commit

1. Environment Check (MANDATORY FIRST STEP)

MUST cache GPG passphrase if available

# If GPG_PASSPHRASE is set, cache it to gpg-agent
if [ -n "$GPG_PASSPHRASE" ]; then
  gpg --batch --pinentry-mode loopback \
      --passphrase-file <(echo "$GPG_PASSPHRASE") \
      --clearsign >/dev/null 2>&1 <<< "test" && echo "✅ GPG passphrase cached" || echo "❌ GPG cache failed"
else
  echo "⚠️  GPG_PASSPHRASE not set - GPG signing will prompt for passphrase (and fail in non-interactive environment)"
fi

Why this matters

• GPG_PASSPHRASE purpose: Allow GPG to sign automatically without interactive password prompt
• If GPG_PASSPHRASE is set → Must cache first, otherwise git commit --gpg-sign will fail
• If GPG_PASSPHRASE not set → GPG will attempt interactive password prompt (fails in Claude Code environment)

GPG signing decision

• Whether to use --gpg-sign should be determined by project policy or git config
• In this project: always use --gpg-sign (assumes GPG is configured)