di-sukharev / di-sukharev/opencommit
[Feature]: Allow fully custom prompts
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
Why: The prompt modification options will never replicate the simplicity and customization of simply writing the prompt yourself. Users should have the choice. Allowing them to print out the prompt that would be used will give a starting point.
Suggested Solution
- Add config option OCO_CUSTOM_PROMPT: it will ignore all other prompt-manipulating options and set the prompt to exactly what the user specifies.
- Add an oco --show-prompt flag: prints to stdout the prompt that would be used (don't do anything)
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 entry point for oco --show-prompt, the configuration handling for OCO_CUSTOM_PROMPT, and the code that assembles the prompt. Verify how existing prompt options are applied. Done means the custom value takes precedence, the flag prints the effective prompt and exits without other actions, and relevant behavior is covered by the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100