3 files changed, 0 insertions, 46 deletions
diff --git a/configs/users/fcuny/llm/templates/commit-prompt.yaml b/configs/users/fcuny/llm/templates/commit-prompt.yaml
deleted file mode 100644
index f9a2752..0000000
--- a/configs/users/fcuny/llm/templates/commit-prompt.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-model: claude-3.7-sonnet
-prompt: >
-  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
-  - Remember to mention the files that were changed, and what was changed
-  - Explain the 'why' behind changes
-  - Use bullet points for multiple changes
-  - Tone: Use some emojis, be funny, and 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]"
-
-  Here's the input: $input
diff --git a/configs/users/fcuny/llm/templates/pr-prompt.yaml b/configs/users/fcuny/llm/templates/pr-prompt.yaml
deleted file mode 100644
index 53671ba..0000000
--- a/configs/users/fcuny/llm/templates/pr-prompt.yaml
+++ /dev/null
@@ -1,15 +0,0 @@
-model: claude-3.7-sonnet
-prompt: >
-  Write a clear, informative pull request message in markdown:
-
-  * Start with a summary
-  * Remember to mention the files that were changed, and what was changed
-  * Explain the 'why' behind changes
-  * Include a bulleted list to outline all of the changes
-  * If there are no changes, or the input is blank - then return a blank string
-
-  Think carefully before you write your pull request body.
-
-  What you write will be passed to create a github pull request
-
-  Text to use for the pull request message: $input
diff --git a/configs/users/fcuny/llm/templates/readme-gen.yaml b/configs/users/fcuny/llm/templates/readme-gen.yaml
deleted file mode 100644
index 585aaf2..0000000
--- a/configs/users/fcuny/llm/templates/readme-gen.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-system: You are a senior product engineer. you are responsible for making, documenting and creating great code, products and successful companies. write a readme for this repo in markdown. my github username is fcuny.
-  - Use emojis.
-  - Make sure the document order is Summary of project, How to use, Tech info
-  - The readme is the first thing a person will read about the project. Be thorough.
-  - Use markdown formatting.
-  - Use code blocks for code.