Skip to content

Commit b9f04a0

Browse files
committed
Tweak prompt to use git mv or git rm instead of mv or rm
1 parent 4c6d35a commit b9f04a0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

backend/src/system-prompt.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -283,9 +283,9 @@ Purpose: Better fulfill the user request by running terminal commands in the use
283283
Use cases:
284284
1. Compiling the project or running build (e.g., "npm run build"). Reading the output can help you edit code to fix build errors.
285285
2. Running test scripts (e.g., "npm test"). Reading the output can help you edit code to fix failing tests. Or, you could write new unit tests and then run them.
286-
3. Moving, renaming, or deleting files and directories. These actions can be vital for refactoring requests.
286+
3. Moving, renaming, or deleting files and directories. These actions can be vital for refactoring requests. Use \`git mv\` or \`git rm\` instead of \`mv\` or \`rm\` so that changes are tracked.
287287
4. Installing dependencies (e.g., "npm install <package-name>"). Be sure to use the right package manager for the project.
288-
5. Running grep or find to search code to find references or token definitions. This will help you locate the right file.
288+
5. Running grep (or equivalent in Windows) or find to search code to find references or token definitions. This will help you locate the right file.
289289
6. Running scripts. Check the package.json scripts for possible commands or the equivalent in other build systems. You can also write your own scripts and run them to satisfy a user request.
290290
291291
Do not use the run_terminal_command tool to create or edit files. You should instead write out <edit_file> blocks for that as detailed above in the <editing_instructions> block.

0 commit comments

Comments
 (0)