diff options
| author | Franck Cuny <59291+fcuny@users.noreply.github.com> | 2025-02-24 19:24:13 -0800 |
|---|---|---|
| committer | Franck Cuny <59291+fcuny@users.noreply.github.com> | 2025-02-24 19:24:47 -0800 |
| commit | c4fecf6bfdaa846c5657b82325501047189aed5d (patch) | |
| tree | 76ad80e14276d4a184b3c7a0b921641e1d78b7a4 /configs/prompts/commit-system-prompt.txt | |
| parent | add ~/.local/bin to the path (diff) | |
| download | infra-c4fecf6bfdaa846c5657b82325501047189aed5d.tar.gz | |
🤖 Add LLM tooling and prompts for Git workflow automation
- Add new section in README about LLM tooling installation
- Create prompts directory with templates for commit and PR messages
- Add new llm.nix module with:
- Configuration for prompt file locations
- Fish shell aliases for generating commit and PR messages using Claude 3.5
- Add `llm` recipe in justfile to install llm CLI tool and Anthropic provider
- Integrate LLM module into home-manager configuration
The changes introduce automation for generating high-quality commit messages and PR descriptions using AI, while keeping the prompts configurable and version controlled.
Diffstat (limited to 'configs/prompts/commit-system-prompt.txt')
| -rw-r--r-- | configs/prompts/commit-system-prompt.txt | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/configs/prompts/commit-system-prompt.txt b/configs/prompts/commit-system-prompt.txt new file mode 100644 index 0000000..8ddc434 --- /dev/null +++ b/configs/prompts/commit-system-prompt.txt @@ -0,0 +1,20 @@ +Write a concise, informative commit message for these changes: +- Review the whole context of the diff carefully to see what effect the change would have on the rest of the code and explain that. Be specific about the effect. +- Do not guess about intent. +- The goal of this commit message is that someone familiar with the codebase, but not with these changes would understand why the changes were made and what was changed. +- The first line should be a short summary of the changes +- Explain the 'why' behind changes +- Use bullet points for multiple changes +- Tone: Use some emojis, be funny, expressive, but stay professional +- If there are no changes, or the input is blank - then return a blank string + +Think carefully about what would be most helpful to someone trying to understand the intent of this commit before you write your commit message. Your commit message will be used as an example to train other team members about the content of a good commit message. + +The output format should be: + +Summary of changes +- changes +- changes +and so on + +What you write will be passed directly to git commit -m "[message]" |