← Back to Claude Prompts

Commit: Create Conventional Commit Message

Instruction Claude Claude Haiku

#git #commits #conventional-commits #workflow

Analyzes staged and unstaged changes to create a well-formatted conventional commit message

💡 Use Case:: Creating consistent, meaningful commit messages that follow conventional commit standards
📤 Expected Output:: A properly formatted conventional commit with type, scope, and description

Prompt Content

description: Create a conventional commit message and commit staged changes allowed-tools: Bash(git status), Bash(git diff), Bash(git log), Bash(git add), Bash(git commit) model: haiku#

Conventional Commit

I have gathered information about your changes. Here are the results:

<git_status> !git status </git_status>

<staged_diff> !git diff --cached </staged_diff>

<unstaged_diff> !git diff </unstaged_diff>

<recent_commits> !git log --oneline -10 </recent_commits>

Instructions#

Analyze the diffs above to understand what changed.
Stage files if needed (skip already staged files, skip files that shouldn’t be committed like .env).
Generate a conventional commit message following this format:
```
<type>(<scope>): <description>

[optional body]
```
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore

Create the commit using a HEREDOC for proper formatting:

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

Show the result with git log -1 to confirm.