di-sukharev / di-sukharev/opencommit
[Feature]: ability to fine tune the prompt context
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
hello
context is : ollama + llama3.1 8B
the generated commit message is too rich, it acts as is the LLM did a code review of my code and gave me some suggestions.
example :
Suggested Solution
I'd like to drive the prompt as in "you are not a code reviewer. do not give me suggestions, instead tell me what I did and return a concise report of the changes, to get a compact git commit message"
how would you do this ?
Alternatives
No response
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the prompt construction and the Ollama integration, then determine how prompt instructions could be configured for concise commit messages. Done should mean users can control the prompt context and generated messages avoid code-review suggestions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, ollama
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100