agent-prompt-recent-message-summarization

name	Agent Prompt: Recent Message Summarization
description	Agent prompt used for summarizing recent messages.
ccVersion	2.1.139
allowed-tools	Read Write Edit Bash
license	BSD-3-Clause license
metadata	{"skill-author":"Lord1Egypt"}

Your task is to create a detailed summary of the RECENT portion of the conversation — the messages that follow earlier retained context. The earlier messages are being kept intact and do NOT need to be summarized. Focus your summary on what was discussed, learned, and accomplished in the recent messages only.

${`Before providing your final summary, wrap your analysis in tags to organize your thoughts and ensure you've covered all necessary points. In your analysis process:

1. Analyze the recent messages chronologically. For each section thoroughly identify:
   • The user's explicit requests and intents
   • Your approach to addressing the user's requests
   • Key decisions, technical concepts and code patterns
   • Specific details like:
     • 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.
   • Note any security-relevant instructions or constraints the user stated (e.g., sensitive files or data to avoid, operations that must not be performed, credential or secret handling rules). These MUST be preserved verbatim in the summary so they continue to apply after compaction.
2. Double-check for technical accuracy and completeness, addressing each required element thoroughly.`}

Your summary should include the following sections:

1. Primary Request and Intent: Capture the user's explicit requests and intents from the recent messages
2. Key Technical Concepts: List important technical concepts, technologies, and frameworks discussed recently.
3. Files and Code Sections: Enumerate specific files and code sections examined, modified, or created. Include full code snippets where applicable and include a summary of why this file read or edit is important.
4. Errors and fixes: List errors encountered and how they were fixed.
5. Problem Solving: Document problems solved and any ongoing troubleshooting efforts.
6. All user messages: List ALL user messages from the recent portion that are not tool results. Preserve any security-relevant instructions or constraints verbatim so they remain in effect after compaction.
7. Pending Tasks: Outline any pending tasks from the recent messages.
8. Current Work: Describe precisely what was being worked on immediately before this summary request.
9. Optional Next Step: List the next step related to the most recent work. Include direct quotes from the most recent conversation.

Here's an example of how your output should be structured:

[Your thought process, ensuring all points are covered thoroughly and accurately]

1. Primary Request and Intent: [Detailed description]

2. Key Technical Concepts:

   • [Concept 1]
   • [Concept 2]

3. Files and Code Sections:

   • [File Name 1]
     • [Summary of why this file is important]
     • [Important Code Snippet]

4. Errors and fixes:

   • [Error description]:
     • [How you fixed it]

5. Problem Solving: [Description]

6. All user messages:

   • [Detailed non tool use user message]

7. Pending Tasks:

   • [Task 1]

8. Current Work: [Precise description of current work]

9. Optional Next Step: [Optional Next step to take]

Please provide your summary based on the RECENT messages only (after the retained earlier context), following this structure and ensuring precision and thoroughness in your response.