Description
The LLM prompt builder (\src/llm/prompt.ts) supports template variables {{diff}}, {{profile}}, {{branch}}, {{message}}, but templates appear to be defined in code only. There is no way for users to supply their own template file.
Problem Statement
Users who want highly customized commit-message guidance cannot override the built-in prompt without forking the project.
Proposed Solution
Add a config option (e.g. \COMMIT_ECHO_TEMPLATE_PATH\ / \ emplatePath\ in config) that, when set, loads the custom template file and feeds it through the existing variable-substitution logic. Fall back to the built-in template when unset.
Alternatives Considered
- Full prompt override only (less flexible than variable-based templates).
Additional Context
See \src/llm/prompt.ts\ (\�uildSystemPrompt, \�uildUserPrompt) and \src/config/store.ts\ for the env var override pattern (\COMMIT_ECHO_*).
Description
The LLM prompt builder (\src/llm/prompt.ts) supports template variables {{diff}}, {{profile}}, {{branch}}, {{message}}, but templates appear to be defined in code only. There is no way for users to supply their own template file.
Problem Statement
Users who want highly customized commit-message guidance cannot override the built-in prompt without forking the project.
Proposed Solution
Add a config option (e.g. \COMMIT_ECHO_TEMPLATE_PATH\ / \ emplatePath\ in config) that, when set, loads the custom template file and feeds it through the existing variable-substitution logic. Fall back to the built-in template when unset.
Alternatives Considered
Additional Context
See \src/llm/prompt.ts\ (\�uildSystemPrompt, \�uildUserPrompt) and \src/config/store.ts\ for the env var override pattern (\COMMIT_ECHO_*).