AI Prompts for Managing Context Loss in Sessions

Please provide a detailed summary of the last five changes made to the codebase. For each change, include the specific files affected, the nature of the modifications, and the date they were implemented. Additionally, analyze these changes for any inconsistencies or overlooked instructions that may impact functionality. Highlight any potential issues that could arise from these changes and suggest possible solutions or next steps to address them.

Please review the current project tree and analyze its structure. Identify any files that appear to have lost context or are not aligned with the overall project goals. For each file, provide a brief explanation of the discrepancies you find, including potential reasons for the loss of context and suggestions for how to resolve these issues. Format your findings in a clear, organized manner, and include any recommendations for improving the project tree's coherence.

Please analyze the session history and summarize the key instructions and decisions made earlier. Identify any discrepancies or changes in direction compared to the current state of the project. Highlight specific areas where the project's trajectory may have shifted and provide insights on potential impacts. Additionally, suggest any adjustments or considerations that should be taken into account moving forward.

Identify specific areas where context appears to be missing in the current discussion. For each identified gap, provide a detailed explanation of why this context may be lacking, considering factors such as incomplete information, assumptions made, or potential misunderstandings. Additionally, suggest strategies to address these gaps and improve overall clarity in the conversation. Format your response in a structured way, listing each gap with its corresponding reasons and solutions.

Please review the contents of the .cursorrules file and evaluate whether the current actions being taken comply with the specified rules. Identify and highlight any deviations from the established guidelines, providing specific examples of where the actions do not align. Additionally, suggest potential adjustments or corrections that could be made to ensure full compliance with the .cursorrules. Format your findings in a clear report that includes sections for compliance status, deviations noted, and recommendations for improvement.

Please help me restore the lost instructions for my project. I need you to identify the specific parts of the code that require adjustments to align with the original instructions. Provide a detailed explanation of what changes are necessary, including any relevant code snippets or examples. Additionally, outline the implications of these adjustments on the overall functionality of the project and any potential issues that may arise from the changes.

Identify files that exhibit inconsistencies resulting from context loss. Provide a detailed, step-by-step guide on how to analyze these files, pinpoint the specific inconsistencies, and implement corrections effectively. Include examples of common types of inconsistencies that may arise and suggest best practices for maintaining context in future file management. Format the guide in a clear, numbered list for easy reference, ensuring that each step is actionable and straightforward.

Please review the project rules outlined in the .cursorrules file and summarize them in a clear and concise manner. Highlight any key points that are critical for compliance in future actions. Additionally, provide recommendations on how to effectively communicate these rules to the team to ensure everyone understands and adheres to them moving forward. Format the summary as a bullet-point list for easy reference.

Please review the following code and identify areas where context may have been lost. Add detailed comments that explain the purpose and functionality of each section, particularly focusing on complex logic or any non-obvious decisions made. The comments should serve as guidance for future developers to understand the code better and prevent similar issues from occurring. Ensure that the comments are clear, concise, and provide enough information to make the code self-explanatory.

Please summarize the key points of our current session and ensure that all ongoing actions align with these points. Include any relevant details that have been discussed so far, such as objectives, decisions made, and any outstanding tasks. Additionally, clarify how each action contributes to our overall goals and if there are any adjustments needed to stay on track. Provide this summary in a structured format that is easy to follow.

Please verify that the context has been fully restored after the session interruption. Identify and list any remaining issues that may still exist, providing details on each one. Additionally, confirm whether these issues have been addressed and resolved, and if not, suggest potential solutions or next steps to ensure a complete restoration of context.

Please conduct a thorough consistency check across the entire project. Identify any discrepancies or misalignments with the intended context and provide a detailed report of your findings. Include specific sections or components that do not align, along with suggestions for how to correct them. Ensure that the results are clearly formatted for easy review, highlighting any critical issues that need immediate attention.

Please test the project against the [RULES FILE NAME] to ensure compliance with all specified rules. Provide a detailed report that outlines any actions that do not meet the compliance standards, including specific examples of non-compliance and suggestions for how to rectify these issues. Additionally, confirm which actions successfully comply with the rules and summarize the overall compliance status of the project. Format the report in a clear, structured manner with sections for compliance, non-compliance, and recommendations.

Please review the newly added code comments in the project. Assess whether each comment provides clear and concise guidance that will help prevent future context loss for developers. Identify any comments that may be vague or unclear, and suggest improvements to enhance their clarity and usefulness. Additionally, provide a summary of your findings, highlighting the strengths and weaknesses of the current comments, and recommend best practices for writing effective code comments moving forward.

Recreate the original scenario that led to the context loss during the session. Provide a detailed description of the steps taken that resulted in the loss of context, including any specific actions or inputs that were involved. After outlining the original scenario, confirm whether the issue still occurs by demonstrating the current behavior in a similar situation. Present a clear comparison of the before and after states, highlighting any changes or resolutions that have been implemented to address the context loss issue.

Draft a new rule for the .cursorrules file that addresses the recent issue of context loss during sessions. The rule should specify the conditions under which context loss occurs and outline the preventive measures to be implemented. Include details on how to monitor for context retention, the expected behavior of the system when the rule is applied, and any necessary adjustments to existing rules that may conflict with this new rule. Format the rule clearly and ensure it is easy to understand and implement.

Create a comprehensive checklist to use at the beginning of each session to ensure that context is maintained throughout. Include items such as reviewing the previous session's key points, setting clear objectives for the current session, confirming all necessary resources and materials are ready, and establishing a communication plan for any interruptions. The checklist should be structured in a way that allows for easy tracking of completed items and should be formatted for quick reference during the session. Aim for at least 10 specific checklist items that can be adapted for various types of sessions.

Please generate a set of persistent comments that can be added to the codebase to warn developers about actions that may lead to context loss. The comments should be clear and concise, explaining the potential risks associated with specific actions or code patterns. Include at least five examples of comment text that can be directly inserted into the code, and ensure that each comment is accompanied by a brief explanation of the context in which it should be used. Format the output in a way that makes it easy to copy and paste into the code.

Please create a detailed protocol for maintaining context during long sessions. The protocol should include strategies for ensuring continuity, such as regular summaries of key points discussed, methods for tracking action items, and techniques for re-engaging participants if the conversation strays. Additionally, provide a concise summary of this protocol that can be easily referenced at a glance. Format the protocol in a clear, step-by-step manner, and ensure it covers at least five key strategies.

I need help developing a context tracking tool that can maintain continuity throughout a session. Please suggest a detailed method or framework for tracking context effectively. Include specific steps for implementation, such as how to gather and store context data, how to retrieve it during sessions, and any best practices for ensuring accuracy and reliability. Additionally, outline potential challenges in maintaining context and ways to address them.