di-sukharev / di-sukharev/opencommit
[Feature]: Summarise git commit message
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
opencommit feature tends to generate quite a chunk of text for commit messages when descriptions are set. Detailed? Yes. But a bit long to read? Probably.
What if we add a feature that lets us summarise these commit messages after the initial commit?
Suggested Solution
- After making a commit, the system would check if the commit message is getting lengthy.
- If it is, it could then pop a question, asking if you'd like to summarise the commit message.
- If you say yes it generates a neat, concise summary of your commit message, keeping the important stuff and skipping the fluff.
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
The issue does not name files, tests, or entry points, so first trace where opencommit creates and finalizes Git commit messages. Define the length threshold, prompt behavior, summary generation path, and success criteria with maintainers before implementation; verify the resulting commit message and user flow with tests.
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
- 25/100