git_commit tool should take filename
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16
- Forks
- 3
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 121
Description
Like git commit, jp-tools git_commit should optionally work from file contents. My process includes reviewing specific proposed commit messages, then sometimes editing them manually, and there is no need to (wait and) ask the LLM to regenerate those tokens.
I have previously built this tool into my own workflow, and this isn't a dealbreaker to maintain separately, but it would be more handy to have the feature updated for me rather than maintained locally.
Contributor guide
No contributing guide indexed for this repository
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 at the git_commit CLI entry point and trace how it currently receives or generates commit-message contents. Add optional filename support while preserving the existing workflow, then verify that manually supplied file contents are used without asking the LLM to regenerate them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100