di-sukharev / di-sukharev/opencommit
[Feature]: add context for WHY in 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
lets help ai to understand why the changes were done
Suggested Solution
a flag: oco -- why="string"
mb string can be ticket description
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
Start by locating the CLI option handling and the code that builds the AI prompt for generated commit messages. Determine how an optional WHY value should be passed through and verify that the resulting commit message generation includes it without changing behavior when the option is absent.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100