zach
/
RA.Aid
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Improve prompts.

This commit is contained in:
user 2024-12-23 09:39:29 -05:00
parent 6e7b41a354
commit 29448b006b
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
ra_aid/prompts.py
View File

@ -370,6 +370,7 @@ You have often been criticized for:
- Overcomplicating things.
- Doing the same work over and over across tasks.
- Asking the user if they want to implement the plan (you are an *autonomous* agent, with no user interaction unless you use the ask_human tool explicitly).
- Announcing that you will use a tool when you should be just quietly using it.
"""
# Implementation stage prompt - guides specific task implementation
@ -419,6 +420,13 @@ Testing:
- Only test things that can be tested by an automated process.
Once the task is complete, ensure all updated files are emitted.
You have often been criticized for:
- Overcomplicating things.
- Doing changes outside of the specific scoped instructions.
- Doing the same work over and over across tasks.
- Asking the user if they want to implement the plan (you are an *autonomous* agent, with no user interaction unless you use the ask_human tool explicitly).
- Announcing that you will use a tool when you should be just quietly using it.
"""
# New agentic chat prompt for interactive mode
@ -484,8 +492,9 @@ Remember:
You have often been criticized for:
- You have a tendency to leave out key details and information that the user just gave you, while also needlessly increasing scope.
- You sometimes call request_research_and_implementation which makes the full implementation successfully, but act like it has only been planned and still needs to be implemented.
- Interviewing the user too much. Some is good, but keep it sensible and focused on efficiently getting the best result aligned with the user's intention.
- Refusing to use request_research_and_implementation for commands like "commit and push" where you should (that tool can run basic or involved shell commands/workflows).
- Calling request_research for general background knowledge which you already know.
- When the user gives an overly broad request, you make assumptions and request implementation immediately when you should be interviewing the user more.
- Assuming the user is always right. Sometimes they're wrong or mistaken, and you should push back when you feel strongly about this.
- Not confirming with the user before starting a significant implementation task.
"""