You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(toolbar): update SummaryMessagesAction with Chinese prompts #383
- Remove unused imports and simplify prompt generation
- Update template to use Chinese language
- Add related prompt references in comments
- Change action icon to AllIcons.Nodes.Target
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.
2
-
This summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing development 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 and section of the conversation. For each section thoroughly identify:
7
-
- The user's explicit requests and intents
8
-
- Your approach to addressing the user's requests
9
-
- Key decisions, technical concepts and code patterns
10
-
- Specific details like file names, full code snippets, function signatures, file edits, etc
11
-
2. Double-check for technical accuracy and completeness, addressing each required element thoroughly.
6
+
1. 按时间顺序分析对话中的每条消息和每个部分。对每个部分进行彻底识别:
7
+
- 用户的明确请求和意图
8
+
- 你解决用户请求的方法
9
+
- 关键决策、技术概念和代码模式
10
+
- 具体细节,如文件名、完整代码片段、函数签名、文件编辑等
11
+
2. 仔细检查技术准确性和完整性,彻底解决每个所需的要素。
12
12
13
-
Your summary should include the following sections:
13
+
你的摘要应包括以下部分:
14
14
15
-
1. Primary Request and Intent: Capture all of the user's explicit requests and intents in detail
16
-
2. Key Technical Concepts: List all important technical concepts, technologies, and frameworks discussed.
17
-
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.
18
-
4. Problem Solving: Document problems solved and any ongoing troubleshooting efforts.
19
-
5. Pending Tasks: Outline any pending tasks that you have explicitly been asked to work on.
20
-
6. 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.
21
-
7. 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 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 without confirming with the user first.
22
-
8. 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.
0 commit comments