aicommit2 v2.2.7

🚀 Quick Start

# Install globally
npm install -g aicommit2
# Set up at least one AI provider
aicommit2 config set OPENAI.key=<your-key>
# Use in your git repository
git add .
aicommit2

📖 Introduction

aicommit2 is a reactive CLI tool that automatically generates Git commit messages using various AI models. It supports simultaneous requests to multiple AI providers, allowing users to select the most suitable commit message. The core functionalities and architecture of this project are inspired by AICommits.

✨ Key Features

• Multi-AI Support: Integrates with OpenAI, Anthropic Claude, Google Gemini, Mistral AI, Cohere, Groq, Ollama and more.
• OpenAI API Compatibility: Support for any service that implements the OpenAI API specification.
• Reactive CLI: Enables simultaneous requests to multiple AIs and selection of the best commit message.
• Git Hook Integration: Can be used as a prepare-commit-msg hook.
• Custom Prompt: Supports user-defined system prompt templates.

🤖 Supported Providers

• OpenAI
• Anthropic Claude
• Gemini
• Mistral AI (including Codestral)
• Cohere
• Groq
• Perplexity
• DeepSeek
• Ollama
• OpenAI API Compatibility

Setup

⚠️ The minimum supported version of Node.js is the v18. Check your Node.js version with node --version.

1. Install aicommit2:

Directly from npm:

npm install -g aicommit2

Alternatively, from source:

git clone https://github.com/tak-bro/aicommit2.git
cd aicommit2
npm run build
npm install -g .

2. Set up API keys (at least ONE key must be set):

aicommit2 config set OPENAI.key=<your key>
aicommit2 config set ANTHROPIC.key=<your key>
# ... (similar commands for other providers)

3. Run aicommit2 with your staged files in git repository:

git add <files...>
aicommit2

👉 Tip: Use the aic2 alias if aicommit2 is too long for you.

Using Locally

You can also use your model for free with Ollama and it is available to use both Ollama and remote providers simultaneously.

1. Install Ollama from https://ollama.com

2. Start it with your model

ollama run llama3.2 # model you want use. ex) codellama, deepseek-coder

3. Set the host, model and numCtx. (The default numCtx value in Ollama is 2048. It is recommended to set it to 4096 or higher.)

aicommit2 config set OLLAMA.host=<your host>
aicommit2 config set OLLAMA.model=<your model>
aicommit2 config set OLLAMA.numCtx=4096

If you want to use Ollama, you must set OLLAMA.model.

4. Run aicommit2 with your staged in git repository

git add <files...>
aicommit2

👉 Tip: Ollama can run LLMs in parallel from v0.1.33. Please see this section.

How it works

This CLI tool runs git diff to grab all your latest code changes, sends them to configured AI, then returns the AI generated commit message.

If the diff becomes too large, AI will not function properly. If you encounter an error saying the message is too long or it's not a valid commit message, try reducing the commit unit.

Usage

CLI mode

You can call aicommit2 directly to generate a commit message for your staged changes:

git add <files...>
aicommit2

aicommit2 passes down unknown flags to git commit, so you can pass in commit flags.

For example, you can stage all changes in tracked files with as you commit:

aicommit2 --all # or -a

CLI Options

• --locale or -l: Locale to use for the generated commit messages (default: en)
• --all or -a: Automatically stage changes in tracked files for the commit (default: false)
• --type or -t: Git commit message format (default: conventional). It supports conventional and gitmoji
• --confirm or -y: Skip confirmation when committing after message generation (default: false)
• --clipboard or -c: Copy the selected message to the clipboard (default: false).
  • If you give this option, aicommit2 will not commit.
• --generate or -g: Number of messages to generate (default: 1)
  • Warning: This uses more tokens, meaning it costs more.
• --exclude or -x: Files to exclude from AI analysis
• --hook-mode: Run as a Git hook, typically used with prepare-commit-msg hook (default: false)
  • This mode is automatically enabled when running through the Git hook system
  • See Git hook section for more details
• --pre-commit: Run in pre-commit framework mode (default: false)
  • This option is specifically for use with the pre-commit framework

  • See Integration with pre-commit framework section for setup instructions

Example:

aicommit2 --locale "jp" --all --type "conventional" --generate 3 --clipboard --exclude "*.json" --exclude "*.ts"

Git hook

You can also integrate aicommit2 with Git via the prepare-commit-msg hook. This lets you use Git like you normally would, and edit the commit message before committing.

Automatic Installation

In the Git repository you want to install the hook in:

aicommit2 hook install

Manual Installation

if you prefer to set up the hook manually, create or edit the .git/hooks/prepare-commit-msg file:

#!/bin/sh
# your-other-hook "$@"
aicommit2 --hook-mode "$@"

Make the hook executable:

chmod +x .git/hooks/prepare-commit-msg

Uninstall

In the Git repository you want to uninstall the hook from:

aicommit2 hook uninstall

Or manually delete the .git/hooks/prepare-commit-msg file.

Configuration

Reading and Setting Configuration

• READ: aicommit2 config get <key>
• SET: aicommit2 config set <key>=<value>

Example:

aicommit2 config get OPENAI
aicommit2 config get GEMINI.key
aicommit2 config set OPENAI.generate=3 GEMINI.temperature=0.5

Environment Variables

You can configure API keys using environment variables. This is particularly useful for CI/CD environments or when you don't want to store keys in the configuration file.

# OpenAI
OPENAI_API_KEY="your-openai-key"
# Anthropic
ANTHROPIC_API_KEY="your-anthropic-key"
# Google
GEMINI_API_KEY="your-gemini-key"
# Mistral AI
MISTRAL_API_KEY="your-mistral-key"
CODESTRAL_API_KEY="your-codestral-key"
# Other Providers
COHERE_API_KEY="your-cohere-key"
GROQ_API_KEY="your-groq-key"
PERPLEXITY_API_KEY="your-perplexity-key"
DEEPSEEK_API_KEY="your-deepseek-key"

Usage Example:

OPENAI_API_KEY="your-openai-key" ANTHROPIC_API_KEY="your-anthropic-key" aicommit2

Note: Environment variables take precedence over configuration file settings.

How to Configure in detail

1. Command-line arguments: use the format --[Model].[Key]=value

aicommit2 --OPENAI.locale="jp" --GEMINI.temperatue="0.5"

2. Configuration file: use INI format in the ~/.aicommit2 file or use set command. Example ~/.aicommit2:

# General Settings
logging=true
generate=2
temperature=1.0

# Model-Specific Settings
[OPENAI]
key="<your-api-key>"
temperature=0.8
generate=1
systemPromptPath="<your-prompt-path>"

[GEMINI]
key="<your-api-key>"
generate=5
includeBody=true

[OLLAMA]
temperature=0.7
model[]=llama3.2
model[]=codestral

The priority of settings is: Command-line Arguments > Environment Variables > Model-Specific Settings > General Settings > Default Values.

General Settings

The following settings can be applied to most models, but support may vary. Please check the documentation for each specific model to confirm which settings are supported.

👉 Tip: To set the General Settings for each model, use the following command.

aicommit2 config set OPENAI.locale="jp"
aicommit2 config set CODESTRAL.type="gitmoji"
aicommit2 config set GEMINI.includeBody=true

systemPrompt

• Allow users to specify a custom system prompt

aicommit2 config set systemPrompt="Generate git commit message."

systemPrompt takes precedence over systemPromptPath and does not apply at the same time.

systemPromptPath

• Allow users to specify a custom file path for their own system prompt template
• Please see Custom Prompt Template

aicommit2 config set systemPromptPath="/path/to/user/prompt.txt"

exclude

• Files to exclude from AI analysis
• It is applied with the --exclude option of the CLI option. All files excluded through --exclude in CLI and exclude general setting.

aicommit2 config set exclude="*.ts"
aicommit2 config set exclude="*.ts,*.json"

NOTE: exclude option does not support per model. It is only supported by General Settings.

type

Default: conventional

Supported: conventional, gitmoji

The type of commit message to generate. Set this to "conventional" to generate commit messages that follow the Conventional Commits specification:

aicommit2 config set type="conventional"

locale

Default: en

The locale to use for the generated commit messages. Consult the list of codes in: https://wikipedia.org/wiki/List_of_ISO_639_language_codes.

aicommit2 config set locale="jp"

generate

Default: 1

The number of commit messages to generate to pick from.

Note, this will use more tokens as it generates more results.

aicommit2 config set generate=2

logging

Default: true

Option that allows users to decide whether to generate a log file capturing the responses. The log files will be stored in the ~/.aicommit2_log directory(user's home).

• You can remove all logs below comamnd.

aicommit2 log removeAll

includeBody

Default: false

This option determines whether the commit message includes body. If you want to include body in message, you can set it to true.

aicommit2 config set includeBody="true"

aicommit2 config set includeBody="false"

maxLength

The maximum character length of the Subject of generated commit message

Default: 50

aicommit2 config set maxLength=100

timeout

The timeout for network requests in milliseconds.

Default: 10_000 (10 seconds)

aicommit2 config set timeout=20000 # 20s

temperature

The temperature (0.0-2.0) is used to control the randomness of the output

Default: 0.7

aicommit2 config set temperature=0.3

maxTokens

The maximum number of tokens that the AI models can generate.

Default: 1024

aicommit2 config set maxTokens=3000

topP

Default: 0.9

Nucleus sampling, where the model considers the results of the tokens with top_p probability mass.

aicommit2 config set topP=0.2

disabled

Default: false

This option determines whether a specific model is enabled or disabled. If you want to disable a particular model, you can set this option to true.

To disable a model, use the following commands:

aicommit2 config set GEMINI.disabled="true"
aicommit2 config set GROQ.disabled="true"

codeReview

Default: false

The codeReview parameter determines whether to include an automated code review in the process.

aicommit2 config set codeReview=true

NOTE: When enabled, aicommit2 will perform a code review before generating commit messages.

⚠️ CAUTION

• The codeReview feature is currently experimental.
• This feature performs a code review before generating commit messages.
• Using this feature will significantly increase the overall processing time.
• It may significantly impact performance and cost.
• The code review process consumes a large number of tokens.

codeReviewPromptPath

• Allow users to specify a custom file path for code review

aicommit2 config set codeReviewPromptPath="/path/to/user/prompt.txt"

Available General Settings by Model

All AI support the following options in General Settings.

• systemPrompt, systemPromptPath, codeReview, codeReviewPromptPath, exclude, type, locale, generate, logging, includeBody, maxLength

Model-Specific Settings

Some models mentioned below are subject to change.

OpenAI

OPENAI.key

The OpenAI API key. You can retrieve it from OpenAI API Keys page.

aicommit2 config set OPENAI.key="your api key"

OPENAI.model

Default: gpt-4o-mini

The Chat Completions (/v1/chat/completions) model to use. Consult the list of models available in the OpenAI Documentation.

aicommit2 config set OPENAI.model=gpt-4o

OPENAI.url

Default: https://api.openai.com

The OpenAI URL. Both https and http protocols supported. It allows to run local OpenAI-compatible server.

aicommit2 config set OPENAI.url="<your-host>"

OPENAI.path

Default: /v1/chat/completions

The OpenAI Path.

OPENAI.topP

Default: 0.9

The top_p parameter selects tokens whose combined probability meets a threshold. Please see detail.

aicommit2 config set OPENAI.topP=0.2

NOTE: If topP is less than 0, it does not deliver the top_p parameter to the request.

Anthropic

ANTHROPIC.key

The Anthropic API key. To get started with Anthropic Claude, request access to their API at anthropic.com/earlyaccess.

ANTHROPIC.model

Default: claude-3-5-haiku-20241022

Supported:

• claude-3-7-sonnet-20250219
• claude-3-5-sonnet-20241022
• claude-3-5-haiku-20241022
• claude-3-opus-20240229
• claude-3-sonnet-20240229
• claude-3-haiku-20240307

aicommit2 config set ANTHROPIC.model="claude-3-5-sonnet-20240620"

Unsupported Options

Anthropic does not support the following options in General Settings.

• timeout

Gemini

GEMINI.key

The Gemini API key. If you don't have one, create a key in Google AI Studio.

aicommit2 config set GEMINI.key="your api key"

GEMINI.model

Default: gemini-2.0-flash

Supported:

• gemini-2.0-flash
• gemini-2.0-flash-lite
• gemini-2.0-pro-exp-02-05
• gemini-2.0-flash-thinking-exp-01-21
• gemini-2.0-flash-exp
• gemini-1.5-flash
• gemini-1.5-flash-8b
• gemini-1.5-pro

aicommit2 config set GEMINI.model="gemini-2.0-flash"

Unsupported Options

Gemini does not support the following options in General Settings.

• timeout

Mistral

MISTRAL.key

The Mistral API key. If you don't have one, please sign up and subscribe in Mistral Console.

MISTRAL.model

Default: pixtral-12b-2409

Supported:

• codestral-latest
• mistral-large-latest
• pixtral-large-latest
• ministral-8b-latest
• mistral-small-latest
• mistral-embed
• mistral-moderation-latest

Codestral

CODESTRAL.key

The Codestral API key. If you don't have one, please sign up and subscribe in Mistral Console.

CODESTRAL.model

Default: codestral-latest

Supported:

• codestral-latest
• codestral-2501

aicommit2 config set CODESTRAL.model="codestral-2501"

Cohere

COHERE.key

The Cohere API key. If you don't have one, please sign up and get the API key in Cohere Dashboard.

COHERE.model

Default: command

Supported models:

• command-r7b-12-2024
• command-r-plus-08-2024
• command-r-plus-04-2024
• command-r-plus
• command-r-08-2024
• command-r-03-2024
• command-r
• command
• command-nightly
• command-light
• command-light-nightly
• c4ai-aya-expanse-8b
• c4ai-aya-expanse-32b

aicommit2 config set COHERE.model="command-nightly"

Unsupported Options

Cohere does not support the following options in General Settings.

• timeout

Groq

GROQ.key

The Groq API key. If you don't have one, please sign up and get the API key in Groq Console.

GROQ.model

Default: deepseek-r1-distill-llama-70b

Supported:

• qwen-2.5-32b
• qwen-2.5-coder-32b
• deepseek-r1-distill-qwen-32b
• deepseek-r1-distill-llama-70b
• distil-whisper-large-v3-en
• gemma2-9b-it
• llama-3.3-70b-versatile
• llama-3.1-8b-instant
• llama-guard-3-8b
• llama3-70b-8192
• llama3-8b-8192
• mixtral-8x7b-32768
• whisper-large-v3
• whisper-large-v3-turbo
• llama-3.3-70b-specdec
• llama-3.2-1b-preview
• llama-3.2-3b-preview
• llama-3.2-11b-vision-preview
• llama-3.2-90b-vision-preview

aicommit2 config set GROQ.model="deepseek-r1-distill-llama-70b"

Perplexity

PERPLEXITY.key

The Perplexity API key. If you don't have one, please sign up and get the API key in Perplexity

PERPLEXITY.model

Default: sonar

Supported:

• sonar-pro
• sonar
• llama-3.1-sonar-small-128k-online
• llama-3.1-sonar-large-128k-online
• llama-3.1-sonar-huge-128k-online

The models mentioned above are subject to change.

aicommit2 config set PERPLEXITY.model="sonar-pro"

DeepSeek

DEEPSEEK.key

The DeepSeek API key. If you don't have one, please sign up and subscribe in DeepSeek Platform.

DEEPSEEK.model

Default: deepseek-chat

Supported:

• deepseek-chat
• deepseek-reasoner

aicommit2 config set DEEPSEEK.model="deepseek-reasoner"

Ollama

OLLAMA.model

The Ollama Model. Please see a list of models available

aicommit2 config set OLLAMA.model="llama3.1"
aicommit2 config set OLLAMA.model="llama3,codellama" # for multiple models

aicommit2 config add OLLAMA.model="gemma2" # Only Ollama.model can be added.

OLLAMA.model is string array type to support multiple Ollama. Please see this section.

OLLAMA.host

Default: http://localhost:11434

The Ollama host

aicommit2 config set OLLAMA.host=<host>

OLLAMA.auth

Not required. Use when your Ollama server requires authentication. Please see this issue.

aicommit2 config set OLLAMA.auth=<auth>

OLLAMA.key

Not required. Use when your Ollama server requires authentication. Please see this issue.

aicommit2 config set OLLAMA.key=<key>

Few examples of authentication methods:

OLLAMA.timeout

Default: 100_000 (100 seconds)

Request timeout for the Ollama.

aicommit2 config set OLLAMA.timeout=<timeout>

OLLAMA.numCtx

The maximum number of tokens the model can process at once, determining its context length and memory usage. It is recommended to set it to 4096 or higher.

aicommit2 config set OLLAMA.numCtx=4096

Unsupported Options

Ollama does not support the following options in General Settings.

• maxTokens

OpenAI API-Compatible Services

You can configure any OpenAI API-compatible service by adding a configuration section with the compatible=true option. This allows you to use services that implement the OpenAI API specification.

# together
aicommit2 config set TOGETHER.compatible=true
aicommit2 config set TOGETHER.url=https://api.together.xyz
aicommit2 config set TOGETHER.path=/v1
aicommit2 config set TOGETHER.model=meta-llama/Meta-Llama-3.1-8B-Instruct-Turbo
aicommit2 config set TOGETHER.key="your-api-key"

Example configuration:

[TOGETHER]
compatible=true
key=<your-api-key>
url=https://api.together.xyz/v1
model=meta-llama/Meta-Llama-3.1-8B-Instruct-Turbo

[GEMINI_COMPATIBILITY]
compatible=true
key=<your-api-key>
url=https://generativelanguage.googleapis.com
path=/v1beta/openai/
model=gemini-1.5-flash

[OLLAMA_COMPATIBILITY]
compatible=true
key=ollama
url=http://localhost:11434/v1
model=llama3.2

Watch Commit Mode

Watch Commit mode allows you to monitor Git commits in real-time and automatically perform AI code reviews using the --watch-commit flag.

aicommit2 --watch-commit

This feature only works within Git repository directories and automatically triggers whenever a commit event occurs. When a new commit is detected, it automatically: 1. Analyzes commit changes 2. Performs AI code review 3. Displays results in real-time

For detailed configuration of the code review feature, please refer to the codeReview section. The settings in that section are shared with this feature.

⚠️ CAUTION

• The Watch Commit feature is currently experimental
• This feature performs AI analysis for each commit, which consumes a significant number of API tokens
• API costs can increase substantially if there are many commits
• It is recommended to carefully monitor your token usage when using this feature
• To use this feature, you must enable watch mode for at least one AI model:

  aicommit2 config set [MODEL].watchMode="true"

Upgrading

Check the installed version with:

aicommit2 --version

If it's not the latest version, run:

npm update -g aicommit2

Custom Prompt Template

aicommit2 supports custom prompt templates through the systemPromptPath option. This feature allows you to define your own prompt structure, giving you more control over the commit message generation process.

Using the systemPromptPath Option

To use a custom prompt template, specify the path to your template file when running the tool:

aicommit2 config set systemPromptPath="/path/to/user/prompt.txt"
aicommit2 config set OPENAI.systemPromptPath="/path/to/another-prompt.txt"

For the above command, OpenAI uses the prompt in the another-prompt.txt file, and the rest of the model uses prompt.txt.

NOTE: For the systemPromptPath option, set the template path, not the template content

Template Format

Your custom template can include placeholders for various commit options. Use curly braces {} to denote these placeholders for options. The following placeholders are supported:

• {locale}: The language for the commit message (string)
• {maxLength}: The maximum length for the commit message (number)
• {type}: The type of the commit message (conventional or gitmoji)
• {generate}: The number of commit messages to generate (number)

Example Template

Here's an example of how your custom template might look:

Generate a {type} commit message in {locale}.
The message should not exceed {maxLength} characters.
Please provide {generate} messages.

Remember to follow these guidelines:
1. Use the imperative mood
2. Be concise and clear
3. Explain the 'why' behind the change

Appended Text

Please note that the following text will ALWAYS be appended to the end of your custom prompt:

Lastly, Provide your response as a JSON array containing exactly {generate} object, each with the following keys:
- "subject": The main commit message using the {type} style. It should be a concise summary of the changes.
- "body": An optional detailed explanation of the changes. If not needed, use an empty string.
- "footer": An optional footer for metadata like BREAKING CHANGES. If not needed, use an empty string.
The array must always contain {generate} element, no more and no less.
Example response format:
[
  {
    "subject": "fix: fix bug in user authentication process",
    "body": "- Update login function to handle edge cases\n- Add additional error logging for debugging",
    "footer": ""
  }
]
Ensure you generate exactly {generate} commit message, even if it requires creating slightly varied versions for similar changes.
The response should be valid JSON that can be parsed without errors.

This ensures that the output is consistently formatted as a JSON array, regardless of the custom template used.

Integration with pre-commit framework

If you're using the pre-commit framework, you can add aicommit2 to your .pre-commit-config.yaml:

repos:
  - repo: local
    hooks:
      - id: aicommit2
        name: AI Commit Message Generator
        entry: aicommit2 --pre-commit
        language: node
        stages: [prepare-commit-msg]
        always_run: true

Make sure you have:

1. Installed pre-commit: brew install pre-commit
2. Installed aicommit2 globally: npm install -g aicommit2
3. Run pre-commit install --hook-type prepare-commit-msg to set up the hook

Note : The --pre-commit flag is specifically designed for use with the pre-commit framework and ensures proper integration with other pre-commit hooks.

Loading Multiple Ollama Models

You can load and make simultaneous requests to multiple models using Ollama's experimental feature, the OLLAMA_MAX_LOADED_MODELS option.

• OLLAMA_MAX_LOADED_MODELS: Load multiple models simultaneously

Setup Guide

Follow these steps to set up and utilize multiple models simultaneously:

1. Running Ollama Server

First, launch the Ollama server with the OLLAMA_MAX_LOADED_MODELS environment variable set. This variable specifies the maximum number of models to be loaded simultaneously. For example, to load up to 3 models, use the following command:

OLLAMA_MAX_LOADED_MODELS=3 ollama serve

Refer to configuration for detailed instructions.

2. Configuring aicommit2

Next, set up aicommit2 to specify multiple models. You can assign a list of models, separated by commas(,), to the OLLAMA.model environment variable. Here's how you do it:

aicommit2 config set OLLAMA.model="mistral,dolphin-llama3"

With this command, aicommit2 is instructed to utilize both the "mistral" and "dolphin-llama3" models when making requests to the Ollama server.

3. Run aicommit2

aicommit2

Note that this feature is available starting from Ollama version 0.1.33 and aicommit2 version 1.9.5.

Disclaimer and Risks

This project uses functionalities from external APIs but is not officially affiliated with or endorsed by their providers. Users are responsible for complying with API terms, rate limits, and policies.

Contributing

For bug fixes or feature implementations, please check the Contribution Guide.

Contributors ✨

Thanks goes to these wonderful people (emoji key):

If this project has been helpful, please consider giving it a Star ⭐️!

Maintainer: @tak-bro