diff options
| author | Franck Cuny <59291+fcuny@users.noreply.github.com> | 2025-02-28 19:19:53 -0800 |
|---|---|---|
| committer | Franck Cuny <59291+fcuny@users.noreply.github.com> | 2025-02-28 19:19:53 -0800 |
| commit | b9b5aaea288ad81de679cae9eacacbac73e87cff (patch) | |
| tree | 5e32d667d05182f98eff54665b1f48f5d6c025c2 /configs/prompts/commit-system-prompt.txt | |
| parent | 🤖 Add LLM tooling and prompts for Git workflow automation (diff) | |
| download | infra-b9b5aaea288ad81de679cae9eacacbac73e87cff.tar.gz | |
🚀 Refactor LLM config: Move to standardized templates and improve setup
- Migrated prompts from text files to YAML templates in `.config/llm/templates/` directory
- Updated fish shell aliases to use the new template system with `-t` flag instead of reading files
- Enhanced justfile's `llm` target with proper Claude model setup and 1Password integration
- Added `LLM_USER_PATH` environment variable for consistent configuration path
- Fixed PR prompt format to better organize content and remove issue resolution section
- Updated Nix configuration to support the new file structure
The changes standardize our LLM prompt system and make it more maintainable, while improving the setup experience for new users. 🧰
Diffstat (limited to 'configs/prompts/commit-system-prompt.txt')
| -rw-r--r-- | configs/prompts/commit-system-prompt.txt | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/configs/prompts/commit-system-prompt.txt b/configs/prompts/commit-system-prompt.txt deleted file mode 100644 index 8ddc434..0000000 --- a/configs/prompts/commit-system-prompt.txt +++ /dev/null @@ -1,20 +0,0 @@ -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]" |