kilimcininkoroglu/commit

Commit

Creates well-formatted commits with conventional commit messages.

Usage

/commit                  # Auto-detect and handle changes
/commit --all            # Stage all changes including untracked
/commit --staged         # Only commit currently staged files
/commit --modified       # Stage and commit modified files only
/commit --no-verify      # Skip pre-commit hooks
/commit --amend          # Amend the last commit
/commit --wip            # Quick WIP commit
/commit --push           # Auto-push after commit

Context Gathering (MANDATORY FIRST STEP)

Before doing anything else, gather full repository context by running these commands IN PARALLEL:

git status                    # Current state of working tree
git diff HEAD                 # All staged and unstaged changes
git branch --show-current     # Current branch name
git log --oneline -10         # Recent commits for style matching

Repo Style Mimicry

Look at the recent commits gathered above and MATCH the repository's existing commit message style:

• If the repo uses conventional commits (feat:, fix:), follow that
• If the repo uses plain messages ("Add login page"), follow that
• If the repo uses ticket prefixes (JIRA-123: ...), follow that
• If no clear pattern exists, default to conventional commit format below

Git Safety Protocol

• NEVER update the git config
• NEVER skip hooks (--no-verify) unless the user explicitly passes --no-verify
• NEVER use git commit --amend unless the user explicitly passes --amend
• NEVER commit files that likely contain secrets (.env, .env.local, credentials.json, *.pem, *.key, id_rsa, etc.) -- warn the user if detected
• NEVER create empty commits if there are no changes
• NEVER use git commands with -i flag (git rebase -i, git add -i) -- interactive mode is not supported
• NEVER add signatures like "Created by Claude", "Co-authored-by: AI" or similar

Default Behavior

1. Gather context (git status, diff, log, branch) -- all in parallel
2. Scan for secrets in staged/changed files
3. Auto-detect git state and take appropriate action
4. Analyze changes for logical grouping
5. Match repo's commit style from recent commits
6. Create atomic commits with appropriate type

Commit Message Format (Default)

Used when repo has no established style or uses conventional commits:

<type>(<scope>): <subject>

[optional body]

[optional footer(s)]

For multi-line commit messages, use HEREDOC syntax:

git commit -m "$(cat <<'EOF'
type(scope): subject line

Body paragraph explaining the why, not the what.
Additional context if needed.

Footer: value
EOF
)"

Types

| Type | Description | Example | |------------|------------------------------------------|----------------------------------------| | feat | New feature | feat: add user authentication | | fix | Bug fix | fix: resolve memory leak | | docs | Documentation | docs: update API reference | | style | Formatting | style: format code with prettier | | refactor | Code change (no fix/feat) | refactor: extract helper functions | | perf | Performance | perf: optimize database queries | | test | Tests | test: add unit tests for auth | | chore | Maintenance | chore: update dependencies | | ci | CI/CD changes | ci: add GitHub Actions workflow | | security | Security fixes | security: patch XSS vulnerability | | hotfix | Critical hotfix | hotfix: fix login crash | | revert | Revert changes | revert: undo payment refactor |

Extended Types

• lint, move, arch, deps-add, deps-remove, deps-pin
• format, patch, catch, remove, typo, comments, deprecate
• init, seed, ux, a11y, i18n, animation, ui, responsive
• db, analytics, logs, logs-remove, backup, metrics, flags
• release, wip, ci-fix, ci-build, merge, license, breaking
• experiment, mock, snapshots, experimental, dx
• docs-api, docs-readme, types, business, assets, gitignore
• dead, cleanup, validation, thread, offline

Process Flow

1. Gather Context: Run git status, diff HEAD, branch, log --oneline -10 (ALL IN PARALLEL)
2. Security Scan: Check changed files for secrets (.env, keys, credentials)
3. Smart Staging Decision:
   • Staged files exist -> commit only staged
   • No staged but changes exist -> analyze and stage appropriately
   • Untracked files -> ask if they should be included
   • Working tree clean -> report no changes
4. Review Changes: git diff --cached --stat + git diff --cached
5. Match Repo Style: Analyze last 10 commits, adopt their message format
6. Analyze for Logical Grouping: Check if changes belong together, suggest splitting if multiple concerns
7. Create Commit: Use HEREDOC syntax for multi-line, simple -m for single-line

Smart Staging Strategy

| Situation | Action | |----------------------|---------------------------| | Only staged files | Commit staged files | | Only modified files | Auto-stage and commit | | Only untracked files | Prompt for inclusion | | Mixed changes | Interactive staging | | No changes | Report clean state |

Commit Rules

• Imperative mood: "add" not "added"
• First line: max 72 characters
• Atomic commits: single logical change
• No period at end of subject line
• Capitalize first letter of subject
• Focus on "why" not "what" -- the diff shows what changed

When to Split Commits

• Different features or fixes
• Mixed types (feat + fix)
• Unrelated file changes
• Large changes (>100 lines)
• Different modules/packages

Options

| Option | Description | Behavior | |-----------------|----------------------------|---------------------------| | --all | Stage all changes | Includes untracked files | | --staged | Commit only staged | Ignores unstaged changes | | --modified | Stage modified only | Excludes untracked files | | --no-verify | Skip pre-commit hooks | Bypass Husky checks | | --amend | Modify last commit | Edit previous commit | | --push | Auto-push after commit | Push to remote branch | | --wip | Work in progress | Quick WIP commit |