di-sukharev / di-sukharev/opencommit
[Feature]: 3 proposition
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
There are some problem :
- Sometime the response is badly formatted
- Sometime, the model didn't understand fully the purpose of commit
- The commit itself can concern many task (even if it shouldn't)
Suggested Solution
I think it's the best way thing oco can provide more accurate message
I thought of many things but I ended on this
Maybe a ncurse ui with a 'more alternative' button
Alternatives
Tell me if you want to do a call, it would speed up the discussion
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 reviewing the issue discussion and the existing commit-message flow, then clarify whether the goal is formatting, better understanding of commit purpose, support for multiple tasks, or an interactive interface. Done should include agreed behavior and acceptance criteria for the proposed alternatives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100