When I tried to configure the prompt, I encountered some issues.

[DianFanGuo2000]

Below is the content of config.tml:

provider: phind
commitTypes:
    - type: feat
      emoji: ✨
    - type: fix
      emoji: "\U0001F41B"
    - type: docs
      emoji: "\U0001F4DA"
    - type: style
      emoji: "\U0001F48E"
    - type: refactor
      emoji: ♻️
    - type: test
      emoji: "\U0001F9EA"
    - type: chore
      emoji: "\U0001F527"
    - type: perf
      emoji: "\U0001F680"
    - type: build
      emoji: "\U0001F4E6"
    - type: ci
      emoji: "\U0001F477"
lockFiles:
    - go.mod
    - go.sum
authorName: ai-commit
authorEmail: ai-commit@example.com

promptTemplate: "Write a concise, clear, and informative commit message based on the conventional commit specification.\n\n- Format: `<type>(<scope>): <description>`\n\n- Accurately classify the commit type (see below). If uncertain, provide the best guess:\n  - feat: A new feature for the user. Functionality changes that are user-facing.\n  - fix: A bug fix.\n  - docs: Changes to documentation.\n  - style: Code style changes.\n  - refactor: Code changes that neither fix a bug nor add a feature. Only use for code changes that do not change functionality or are user-facing.\n  - test: Adding or correcting tests.\n  - chore: Maintenance, project config or auxiliary tool changes.\n\n- Accurately classify the commit scope (see below). If uncertain, provide the best guess:\n  - Noun describing a section of the codebase.\n  - Examples: areas, contacts, containers, orders, prices, settings, statistics, core, ui, config, yarn, gradle, deps, github-actions, release.\n\n- Use present tense and active voice.\n\n- Subject:\n  - Start with a lowercase letter and avoid ending with a period.\n  - Encapsulate any code, numbers, or filenames in backticks.\n\n- Body (optional):\n  - Only add really relevant information that is not already covered by the subject.\n  - If it really matters, provide a detailed explanation of what was changed, why it was changed, and its impact.\n\nEach line MUST NOT exceed 72 characters; wrap in the body if necessary!\n\nUse English language to answer and do not embed the response in a code block. Note, directly output the content for git commit -m <content>, without any extra information feedback."

After that, ai-commit kept returning the same fixed response as shown below:

Then, I tried to reset the prompt to an empty string "", but it still returned the following response:

[DianFanGuo2000]

ok, i switch the model to deepseek, then it can work again. what wrong with the phind model, its ability is not strong enough????

[DianFanGuo2000]

by the way, i found ai-commit will analyse all the diffs, rather than only the git-added files, is it a bug? i think it is

[DianFanGuo2000]

I change the git.go to fix this bug i think, which is below:

git.go.txt