di-sukharev / di-sukharev/opencommit
[Feature]: One Liner and Simpler Commits
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
The commit messages it generates are usually too descriptive and don't look like something a human would write
Suggested Solution
I want to have a way to make the commit messages not only be one line but also be generated just from the file names that have changed
Or, let the commits generate in a way that wouldn't require a lot of tokens
Token limit, or context limit that when reached would generate the message from what it got
It should give an overall overview of what has changed and not go into the details
Alternatives
None
Additional Context
Could be just a flag or let it autodetect that based on the amount of changes
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 existing commit-message generation flow and its handling of changed files and token limits. Done means the tool can produce a concise one-line overview from changed filenames or bounded context, using either a flag or automatic detection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100