alex/g3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated the prompt

Browse Source
This commit is contained in:
Jochen
2025-11-26 10:21:29 +11:00
parent c19127f809
commit c419833ddf
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
crates/g3-planner/src/prompts.rs
View File

@@ -23,16 +23,15 @@ Your task is to analyze the codebase overview provided below and generate shell
you deem most relevant to the requirements given below. you deem most relevant to the requirements given below.
Your output MUST include: Your output MUST include:
1. retain as much information of that as you consider relevant to the request and your next job (not to be attempted yet) 1. A summary report. Use the heading {{SUMMARY BASED ON INITIAL INFO}}.
for planning the main tasks for what you will implement. Ideally that should not be more than 10000 tokens. Write a section - retain as much information of that as you consider relevant to the requirements, and for making an implementation plan.
that you will later use in your next phase, which is detailed implementation plan. Use the heading {{SUMMARY BASED ON INITIAL - Ideally that should not be more than 10000 tokens.
INFO}}. 2. A list of shell commands to explore the code. Use the heading {{CODE EXPLORATION COMMANDS}}.
2. Based on the initial summary, try plan ahead for what you need for a deep dive into the code. Do pay attention that - Try plan ahead for what you need for a deep dive into the code. Make sure the information is sparing.
the information should be sparing. - Carefully consider which commands give you the most relevant information, pick the top 25 commands.
- Use tools like `ls`, `rg` (ripgrep), `grep`, `sed`, `cat`, `head`, `tail` etc. - Use tools like `ls`, `rg` (ripgrep), `grep`, `sed`, `cat`, `head`, `tail` etc.
- Focus on commands that will help understand the code STRUCTURE without dumping large sections of file. - Focus on commands that will help understand the code STRUCTURE without dumping large sections of file.
- e.g. for Rust you might try `rg --no-heading --line-number --with-filename --max-filesize 500K -g '*.rs' '^(pub )?(struct|enum|type|union)` - e.g. for Rust you might try `rg --no-heading --line-number --with-filename --max-filesize 500K -g '*.rs' '^(pub )?(struct|enum|type|union)`
- Mark the beginning and end of the commands with "```". - Mark the beginning and end of the commands with "```".
- Carefully consider which commands give you the most relevant information, make it a maximum of 20.
DO NOT ADD ANY COMMENTS OR OTHER EXPLANATION IN THE COMMANDS SECTION, JUST INCLUDE THE SHELL COMMANDS."#; DO NOT ADD ANY COMMENTS OR OTHER EXPLANATION IN THE COMMANDS SECTION, JUST INCLUDE THE SHELL COMMANDS."#;