apunkt/MetaGPT
1
0
Fork 0
mirror of https://github.com/FoundationAgents/MetaGPT.git synced 2026-05-15 11:02:36 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

update prompt

Browse source
This commit is contained in:
hongjiongteng 2024-06-20 15:40:56 +08:00
parent 6c4cb765c7
commit 050bec2ccf
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
metagpt/prompts/di/engineer2.py
View file

@ -4,12 +4,12 @@ EXTRA_INSTRUCTION = """
4. Each time you write a code in your response, write with the Editor directly without preparing a repetitive code block beforehand.
5. Take on ONE task and write ONE code file in each response. DON'T attempt all tasks in one response.
6. When not specified, you should write files in a folder named "src". If you know the project path, then write in a "src" folder under the project path.
7. When provided system design or project schedule, read them first, then adhere to them in your implementation.
7. When provided system design or project schedule, read them first, then adhere to them in your implementation, especially in the programming language, package, or framework. You MUST implement all code files prescribed in the system design or project schedule. You can create a plan first with each task corresponding to implementing one code file.
8. Write at most one file per task, do your best to implement THE ONLY ONE FILE. CAREFULLY CHECK THAT YOU DONT MISS ANY NECESSARY CLASS/FUNCTION IN THIS FILE.
9. COMPLETE CODE: Your code will be part of the entire project, so please implement complete, reliable, reusable code snippets.
10. When provided system design, YOU MUST FOLLOW "Data structures and interfaces". DONT CHANGE ANY DESIGN. Do not use public member functions that do not exist in your design.
11. Write out EVERY CODE DETAIL, DON'T LEAVE TODO.
12. To modify code in a file, read the entire file, make changes, and use Editor.write instead of Editor.write_content to update the file with the complete code.
12. To modify code in a file, read the entire file, make changes, and update the file with the complete code.
13. Revise task is to use RewriteCode.run to correct code.
14. Only When provided system design, at the end of the plan, add a Revise task for each file; for example, if there are three files, add three Revise tasks.
"""

2
metagpt/roles/di/engineer2.py
View file

@ -11,7 +11,7 @@ class Engineer2(RoleZero):
goal: str = "Take on game, app, and web development"
instruction: str = ENGINEER2_INSTRUCTION
tools: str = ["Plan", "Editor:write,read,write_content", "RoleZero", "RewriteCode"]
tools: str = ["Plan", "Editor:write,read", "RoleZero", "RewriteCode"]
def _update_tool_execution(self):
rewrite_code = RewriteCode()