mirror of
https://github.com/arc53/DocsGPT.git
synced 2025-11-30 17:13:15 +00:00
36 lines
3.4 KiB
Plaintext
36 lines
3.4 KiB
Plaintext
Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions.
|
|
|
|
This summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing work without losing context.
|
|
|
|
Before providing your final summary, wrap your analysis in <analysis> tags to organize your thoughts and ensure you've covered all necessary points. In your analysis process:
|
|
|
|
1. Chronologically analyze each message, tool call and section of the conversation. For each section thoroughly identify:
|
|
- The user's explicit requests and intents
|
|
- Your approach to addressing the user's requests
|
|
- Key decisions, concepts and patterns
|
|
- Specific details like if applicable:
|
|
- file names
|
|
- full code snippets
|
|
- function signatures
|
|
- file edits
|
|
- Errors that you ran into and how you fixed them
|
|
- Pay special attention to specific user feedback that you received, especially if the user told you to do something differently.
|
|
|
|
2. Double-check for accuracy and completeness, addressing each required element thoroughly.
|
|
|
|
Your summary should include the following sections:
|
|
|
|
1. Primary Request and Intent: Capture all of the user's explicit requests and intents in detail
|
|
2. Key Concepts: List all important concepts discussed.
|
|
3. Files and Code Sections: Enumerate specific files and code sections examined, modified, or created. Pay special attention to the most recent messages and include full code snippets where applicable and include a summary of why this file read or edit is important.
|
|
4. Errors and fixes: List all errors that you ran into, and how you fixed them. Pay special attention to specific user feedback that you received, especially if the user told you to do something differently.
|
|
5. Problem Solving: Document problems solved and any ongoing troubleshooting efforts.
|
|
6. All user messages: List ALL user messages that are not tool results. These are critical for understanding the users' feedback and changing intent.
|
|
7. Tool Calls: List ALL tool calls made, including their inputs relevant parts of the outputs.
|
|
8. Pending Tasks: Outline any pending tasks that you have explicitly been asked to work on.
|
|
9. Current Work: Describe in detail precisely what was being worked on immediately before this summary request, paying special attention to the most recent messages from both user and assistant. Include file names and code snippets where applicable.
|
|
10. Optional Next Step: List the next step that you will take that is related to the most recent work you were doing. IMPORTANT: ensure that this step is DIRECTLY in line with the user's most recent explicit requests, and the task you were working on immediately before this summary request. If your last task was concluded, then only list next steps if they are explicitly in line with the users request. Do not start on tangential requests or really old requests that were already completed without confirming with the user first.
|
|
If there is a next step, include direct quotes from the most recent conversation showing exactly what task you were working on and where you left off. This should be verbatim to ensure there's no drift in task interpretation.
|
|
|
|
Please provide your summary based on the conversation and tools used so far, following this structure and ensuring precision and thoroughness in your response.
|