git-commit-sage 0.2.7

A smart Git commit message generator using AI
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61

# Example configuration file for git-commit-sage

[ai]
# The AI model to use
model = "mistralai/Mixtral-8x7B-Instruct-v0.1"
# Temperature for model output (0.0 to 1.0)
temperature = 0.3
# Maximum tokens in response
max_tokens = 100
# Stop sequences for the model
stop_sequences = ["\n"]
# System prompt for the AI
system_prompt = """
You are a highly skilled developer who writes perfect conventional commit messages.
You analyze git diffs and generate commit messages following the Conventional Commits specification.
Your messages are concise, descriptive, and follow the format: type(scope): description.
The type must be one of: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
The scope is optional but should be included when relevant.
The description should be clear and precise, written in imperative mood.
"""
# User prompt template
user_prompt_template = """
Generate a conventional commit message for the following git diff.
The message must follow the exact conventional commit format.
Only return the commit message, nothing else.

Diff:
{}
"""

[git]
# Path to the git repository
repo_path = "."
# Whether to include untracked files in the diff
include_untracked = true
# Whether to show the diff before generating commit message
show_diff = false

[commit]
# List of allowed commit types
allowed_types = [
    "feat",
    "fix",
    "docs",
    "style",
    "refactor",
    "perf",
    "test",
    "build",
    "ci",
    "chore",
    "revert"
]
# Maximum length of commit message
max_length = 72
# Whether to automatically commit after generating message
auto_commit = false
# Whether to verify commit message format
verify_format = true
# Whether to require user confirmation before committing
require_confirmation = true