Smart Conventional Commit

Current State

!git status

Staged Changes

!git diff --staged --stat

Recent Commits (style reference)

!git log --oneline -5

Instructions

Based on the context above, create a professional commit.

Step 1: Security Check

BLOCK and output if secrets detected:

🔒 Security Alert
───────────────────────────────
Found: [file or pattern]
Action: Commit blocked
Fix: Remove sensitive data before committing

Check for:

• .env, .env.* files
• Patterns: password=, secret=, api_key=, token=
• Files: *.pem, *.key, *credentials*

Step 2: Analyze and Detect

Output analysis:

📊 Analysis
───────────────────────────────
Files changed: [X]
Files staged: [Y]
Pattern detected: [type]

Step 3: Generate Message

Format: type(scope): imperative description

FORBIDDEN (NO AI SIGNATURE):

• NEVER add "Co-authored-by: Claude" or any AI mention
• Commit must appear 100% human-written

Step 4: Propose Commit

Output proposal:

📝 Proposed Commit
───────────────────────────────
type(scope): description

[body if needed]
───────────────────────────────

⚡ Ready to commit? [Y/N/E]

Step 5: Execute and Confirm

On confirmation, execute and output:

✅ Committed successfully
───────────────────────────────
Hash: [short-hash]
Message: type(scope): description
Files: [X] changed

Execute with HEREDOC format:

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

If $ARGUMENTS provided, use as hint for the message.