gitkkal commit

Analyzes changes and creates commits following the configured style.

Critical Rules

• NEVER include Co-Authored-By lines in commit messages
• NEVER use git commit --amend — always create NEW commits
• NEVER use git add -A or git add . — stage files individually
• NEVER commit sensitive files (.env, credentials, API keys)
• ALWAYS use HEREDOC for commit messages to ensure proper formatting

Workflow

1. Load Configuration

git rev-parse --show-toplevel  # Find project root

Read {project_root}/.gitkkal/config.json. If not exists, use defaults and display once: "Using default settings. Run /gitkkal:init to customize."

<defaults> ```json { "language": "en", "commitPattern": "conventional", "splitCommits": true, "askOnAmbiguity": true } ``` </defaults>

2. Analyze Changes

git diff --cached --stat    # Staged changes
git diff --cached           # Staged diff
git diff --stat             # Unstaged changes
git status --porcelain      # Untracked files
git log --oneline -10       # Recent commit style reference

Commit candidates (analyze all together):

• Staged changes (index)
• Unstaged changes (modified tracked files)
• Untracked files (new files)

3. User Hint

$ARGUMENTS — If provided, use as guidance for:

• Commit message content/style
• How to split/group changes
• Additional context

The hint is advisory — incorporate appropriately.

4. Decide Commit Splitting

When splitCommits: true:

Principles:

1. Each commit must be an executable unit (passes build/tests)
2. Only semantically cohesive changes in one commit

<good-example> New feature + related tests → One commit </good-example> <bad-example> Bug fix + unrelated new feature → Should be separate commits Formatting + logic changes → Should be separate commits </bad-example>

When askOnAmbiguity: true and splitting is unclear → Use AskUserQuestion.

5. Write Commit Message

Patterns:

Pattern	Format	Example
conventional	<type>[(scope)]: <description>	feat(auth): add login feature
gitmoji	<emoji> [(scope)] <message>	✨ Add login feature
simple	<message>	Add login feature

Types:

Type	Purpose	Gitmoji
feat	New feature	✨
fix	Bug fix	🐛
docs	Documentation	📝
style	Formatting (no logic)	🎨
refactor	Refactoring	♻️
perf	Performance	⚡
test	Tests	✅
build	Build/dependencies	📦
ci	CI config	👷
chore	Other	🔧

Message guidelines:

• Focus on "why" not "what"
• Imperative present tense: "Add", "Fix" (not "Added", "Fixed")
• First line under 50 characters
• Language follows config (ko or en)

6. Execute Commit

# Stage specific files
git add path/to/file1.ts path/to/file2.ts

# Commit with HEREDOC
git commit -m "$(cat <<'EOF'
feat(auth): add social login feature

- Implement OAuth2 flow
- Add session management
EOF
)"

7. Output

Created: abc1234
Message: feat(auth): add social login feature
Files: src/auth.ts, src/session.ts

If multiple commits: show count and summary of each.

Error Handling

Situation	Action
No changes to commit	"No changes to commit."
Pre-commit hook fails	Fix issue, create NEW commit (never amend)
Merge conflict state	"Resolve conflicts before committing."