Add fallback for LLMs without system prompt support #10

New issue

Open

opened 2025-07-06 17:01:42 +00:00 by glenux · 0 comments

glenux commented

2025-07-06 17:01:42 +00:00

Owner

Currently, the commit message generation passes a system parameter to the LLM (model_obj.prompt(..., system=...)). Some older or certain newer models do not accept system prompts and raise exceptions.

This breaks our workflow for those providers.

Why

We want to broaden compatibility so that user-selected models which do not support system prompts can still generate commit messages.
Removing the system prompt entirely is not ideal, because many models rely on it to properly shape their responses.

Proposed Solution

Detect if the selected LLM natively supports system prompts (e.g., check in the model_obj if the info is there).
If unsupported, prepend the system instructions to the user prompt itself.
Retain the existing code path for models that do support system prompts, preserving their behavior.

Currently, the commit message generation passes a `system` parameter to the LLM (`model_obj.prompt(..., system=...)`). Some older or certain newer models do not accept system prompts and raise exceptions. This breaks our workflow for those providers. ## Why * We want to broaden compatibility so that user-selected models which do not support system prompts can still generate commit messages. * Removing the system prompt entirely is not ideal, because many models rely on it to properly shape their responses. ## Proposed Solution 1. Detect if the selected LLM natively supports system prompts (e.g., check in the `model_obj` if the info is there). 2. If unsupported, prepend the system instructions to the user prompt itself. 3. Retain the existing code path for models that do support system prompts, preserving their behavior.