Move tool descriptions to files

Author: Jakub Zika

resources/prompts/tools/eca_directory_tree.txt

@@ -0,0 +1,3 @@
+Returns a recursive tree view of files and directories starting from the specified path.
+The path parameter must be an absolute path, not a relative path.
+**Only works within the directories: $workspaceRoots.**

resources/prompts/tools/eca_edit_file.txt

@@ -0,0 +1,6 @@
+You must use your `eca_read_file` tool to get the file's exact contents before attempting an edit.
+This tool will error if you attempt an edit without reading the file.When crafting the `orginal_content`, you must match the original content from the `eca_read_file` tool output exactly, including all indentation (spaces/tabs) and newlines.
+Never include any part of the line number prefix in the `original_content` or `new_content`.The edit will FAIL if the `original_content` is not unique in the file. To resolve this, you must expand the `new_content` to include more surrounding lines of code or context to make it a unique block.
+ALWAYS prefer making small, targeted edits to existing files. Avoid replacing entire functions or large blocks of code in a single step unless absolutely necessary.
+To delete content, provide the content to be removed as the `original_content` and an empty string as the `new_content`.
+To prepend or append content, the `new_content` must contain both the new content and the original content from `old_string`.

resources/prompts/tools/eca_editor_diagnostics.txt

@@ -0,0 +1,2 @@
+Return editor diagnostics/findings (Ex: LSP diagnostics) for workspaces.
+Only provide the path if you want to get diagnostics for a specific file.

resources/prompts/tools/eca_grep.txt

@@ -0,0 +1,3 @@
+Fast content search tool that works with any codebase size. Finds the paths to files that have matching contents using regular expressions.
+Supports full regex syntax (eg. "log.*Error", "function\\s+\\w+", etc.). Filter files by pattern with the include parameter (eg. "*.js", "*.{ts,tsx}").
+Returns matching file paths sorted by modification time. Use this tool when you need to find files containing specific patterns.

resources/prompts/tools/eca_move_file.txt

@@ -0,0 +1,4 @@
+Move or rename files and directories.
+Can move files between directories and rename them in a single operation.
+If the destination exists, the operation will fail. Works across different directories and can be used for simple renaming within the same directory.
+Both source and destination must be within the directories: $workspaceRoots.

resources/prompts/tools/eca_preview_file_change.txt

@@ -0,0 +1,4 @@
+Preview the FINAL content that will be written to tge file when the plan is accepted.
+Use only for showing definitive implementation, not for iterative exploration.
+When crafting the `orginal_content`, you must match the original content from the `eca_read_file` tool output exactly, including all indentation (spaces/tabs) and newlines.
+For new files, original_content must be empty string.

resources/prompts/tools/eca_read_file.txt

@@ -0,0 +1,3 @@
+Read the contents of a file from the file system. Use this tool when you need to examine the contents of a single file.
+Optionally use the 'line_offset' and/or 'limit' parameters to read specific contents of the file when you know the range.
+Prefer call once this tool over multiple calls passing small offsets. **Only works within the directories: $workspaceRoots.**

resources/prompts/tools/eca_shell_command.txt

@@ -0,0 +1,127 @@
+Executes an arbitrary shell command ensuring proper handling and security measures.
+1. Command Execution:
+  - Always quote file paths that contain spaces with double quotes (e.g., cd \" path with spaces/file.txt \")
+  - Examples of proper quoting:
+    - cd \"/Users/name/My Documents\" (correct)
+    - cd /Users/name/My Documents (incorrect - will fail)
+    - python \"/path/with spaces/script.py\" (correct)
+    - python /path/with spaces/script.py (incorrect - will fail)
+  - After ensuring proper quoting, execute the command.
+  - Capture the output of the command.
+  - VERY IMPORTANT: You MUST avoid using search command `grep`. Instead use eca_grep to search. You MUST avoid read tools like `cat`, `head`, `tail`, and `ls`, and use eca_read_file or eca_directory_tree.
+  - It is very helpful if you write a clear, concise description of what this command does in 5-10 words.
+  - When issuing multiple commands, use the ';' or '&&' operator to separate them. DO NOT use newlines (newlines are ok in quoted strings).
+  - Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it.
+    <good-example>
+    pytest /foo/bar/tests
+    </good-example>
+    <bad-example>
+    cd /foo/bar && pytest tests
+    </bad-example>
+
+# Committing changes with git
+
+When the user asks you to create a new git commit, follow these steps carefully:
+
+1.:
+   - Run a git status command to see all untracked files.
+   - Run a git diff command to see both staged and unstaged changes that will be committed.
+   - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.
+
+2. Analyze all staged changes (both previously staged and newly added) and draft a commit message. Wrap your analysis process in <commit_analysis> tags:
+
+<commit_analysis>
+- List the files that have been changed or added
+- Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.)
+- Brainstorm the purpose or motivation behind these changes
+- Assess the impact of these changes on the overall project
+- Check for any sensitive information that shouldn't be committed
+- Draft a concise (1-2 sentences) commit message that focuses on the \"why\" rather than the \"what\"
+- Ensure your language is clear, concise, and to the point
+- Ensure the message accurately reflects the changes and their purpose (i.e. \"add\" means a wholly new feature, \" update \" means an enhancement to an existing feature, \"fix\" means a bug fix, etc.)
+- Ensure the message is not generic (avoid words like \"Update\" or \"Fix\" without context)
+- Review the draft message to ensure it accurately reflects the changes and their purpose
+</commit_analysis>
+
+3.:
+   - Add relevant untracked files to the staging area.
+   - Create the commit with a message ending with:
+   🤖 Generated with [eca](https://eca.dev)
+
+   Co-Authored-By: eca <[email protected]>
+   - Run git status to make sure the commit succeeded.
+
+4. If the commit fails due to pre-commit hook changes, retry the commit ONCE to include these automated changes. If it fails again, it usually means a pre-commit hook is preventing the commit. If the commit succeeds but you notice that files were modified by the pre-commit hook, you MUST amend your commit to include them.
+
+Important notes:
+- Use the git context at the start of this conversation to determine which files are relevant to your commit. Be careful not to stage and commit files (e.g. with `git add .`) that aren't relevant to your commit.
+- NEVER update the git config
+- DO NOT run additional commands to read or explore code, beyond what is available in the git context
+- DO NOT push to the remote repository
+- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.
+- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
+- Ensure your commit message is meaningful and concise. It should explain the purpose of the changes, not just describe them.
+- Return an empty response - the user will see the git output directly
+- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:
+<example>
+git commit -m \"$(cat <<'EOF'
+   Commit message here.
+
+   🤖 Generated with [eca](https://eca.dev)
+
+   Co-Authored-By: eca <[email protected]>
+   EOF
+   )\"
+</example>
+
+# Creating pull requests
+Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.
+
+IMPORTANT: When the user asks you to create a pull request, follow these steps carefully:
+
+1. In order to understand the current state of the branch since it diverged from the main branch:
+   - Run a git status command to see all untracked files
+   - Run a git diff command to see both staged and unstaged changes that will be committed
+   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote
+   - Run a git log command and `git diff main...HEAD` to understand the full commit history for the current branch (from the time it diverged from the `main` branch)
+
+2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request summary. Wrap your analysis process in <pr_analysis> tags:
+
+<pr_analysis>
+- List the commits since diverging from the main branch
+- Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.)
+- Brainstorm the purpose or motivation behind these changes
+- Assess the impact of these changes on the overall project
+- Do not use tools to explore code, beyond what is available in the git context
+- Check for any sensitive information that shouldn't be committed
+- Draft a concise (1-2 bullet points) pull request summary that focuses on the \"why\" rather than the \"what\"
+- Ensure the summary accurately reflects all changes since diverging from the main branch
+- Ensure your language is clear, concise, and to the point
+- Ensure the summary accurately reflects the changes and their purpose (ie. \"add\" means a wholly new feature, " update " means an enhancement to an existing feature, \"fix\" means a bug fix, etc.)
+- Ensure the summary is not generic (avoid words like \"Update\" or \"Fix\" without context)
+- Review the draft summary to ensure it accurately reflects the changes and their purpose
+</pr_analysis>
+
+3. ALWAYS run the following commands in parallel:
+   - Create new branch if needed
+   - Push to remote with -u flag if needed
+   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.
+<example>
+gh pr create --title \"the pr title\" --body \"$(cat <<'EOF'
+## Summary
+<1-3 bullet points>
+
+## Test plan
+[Checklist of TODOs for testing the pull request...]
+
+🤖 Generated with [eca](https://eca.dev)
+EOF
+)\"
+</example>
+
+Important:
+- NEVER update the git config
+- Return the PR URL when you're done, so the user can see it
+
+# Other common operations
+- View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments

resources/prompts/tools/eca_write_file.txt

@@ -0,0 +1,5 @@
+Create a new file or completely overwrite an existing file with new content.
+This tool will automatically create any necessary parent directories if they don't exist.
+Use this tool when you want to create a new file from scratch or completely replace the entire content of an existing file.
+For partial edits or content replacement within existing files, use eca_edit_file instead.
+**Only works within the directories: $workspaceRoots.**

src/eca/features/tools/editor.clj

@@ -47,8 +47,7 @@
 
 (def definitions
   {"eca_editor_diagnostics"
-   {:description (str "Return editor diagnostics/findings (Ex: LSP diagnostics) for workspaces. "
-                      "Only provide the path if you want to get diagnostics for a specific file.")
+   {:description (tools.util/read-tool-description "eca_editor_diagnostics")
     :parameters {:type "object"
                  :properties {"path" {:type "string"
                                       :description "Optional absolute path to a file to return diagnostics only for that file."}}