AI Prompts for Ensuring Full Error Stack Read

Please display the full error stack trace for the current issue. The initial error message is: [PASTE ERROR MESSAGE]. Additionally, provide a brief explanation of what each part of the stack trace indicates, including any potential causes for the error and suggestions for resolving it. Format your response in a clear, structured manner, with each part of the stack trace explained in separate bullet points for easy understanding.

Please analyze the error stack trace and identify any missing lines that could provide additional context for troubleshooting. I want you to list the lines that are currently present in the stack trace and highlight any gaps or omissions that may be critical for diagnosing the issue. Additionally, provide a brief explanation of how each missing line could contribute to a better understanding of the error. Format your response in a clear, structured manner.

Please confirm whether you have access to the complete context of the error stack trace related to the issue I am facing. If you do not have the full context, please specify which parts of the stack trace are missing or unclear. Additionally, provide any relevant details or suggestions on how to obtain the missing information to help diagnose the problem effectively.

Please analyze the stack trace provided and determine its depth. Include the total number of lines in the stack trace, and provide a summary of the top line and the bottom line, detailing the key information contained in each. Additionally, explain any significant errors or warnings present in the stack trace that may help in diagnosing the issue. Format your response in a clear and structured manner, highlighting the important points for easy reference.

Please analyze the following stack trace: [INSERT STACK TRACE HERE]. Identify the root cause of the error and explain your reasoning. If you are unable to determine the source of the error, specify what additional information or context you would need to make a proper diagnosis. Provide your response in a structured format, detailing each step of your analysis.

Please read and display the entire error stack trace from the current session starting with the initial part: [PASTE INITIAL ERROR]. Ensure that you include all relevant details such as the error type, the file names, line numbers, and any additional context that may help in diagnosing the issue. Format the output clearly, separating each part of the stack trace for easy readability. If there are any common causes or solutions associated with the error, please include those as well.

Please extract and list all lines of the error stack trace for the current issue. Make sure to include every line without omitting any details. Format the output as a numbered list for clarity, and provide a brief explanation of what each line indicates in terms of the error context. Additionally, highlight any specific lines that may point to the root cause of the issue.

Analyze the complete error stack trace provided below and identify the root cause of the issue. Please break down each part of the stack trace, explaining what each line indicates and how it contributes to the overall problem. Additionally, suggest potential solutions or troubleshooting steps to resolve the identified issue. The stack trace is: [INSERT ERROR STACK TRACE HERE].

Please enhance the parsing of the error stack trace to ensure that all lines are included in the output. Provide a detailed explanation of the changes made to the parsing logic and how it improves the accuracy of the stack trace. Additionally, include examples of both the previous and improved outputs to illustrate the differences. Confirm when this enhancement is complete and ready for testing.

Please conduct a full analysis of the error stack trace from the recent diagnostic process. Identify the root causes of the errors and categorize them based on severity and frequency. Provide a detailed report that includes suggested fixes for each identified issue, potential impacts on the system, and any patterns observed in the errors. Format the findings in a clear and organized manner, using bullet points for easy readability.

Please confirm whether you have successfully read the entire error stack trace. Provide a detailed list of all lines in the stack trace, including any relevant error messages, file names, and line numbers. Additionally, explain any potential issues or insights you have gathered from the stack trace that may help in troubleshooting the error. Make sure to format your response clearly for easy reference.

Please analyze the complete stack trace provided and identify the root cause of the error. Explain the reasoning behind your identification, detailing any specific lines or messages in the stack trace that led to your conclusion. Additionally, suggest potential solutions or next steps to resolve the issue based on your findings. Format your response in a clear and structured manner, ensuring it is easy to follow.

Please review the provided error stack trace and identify any missing information that could help in diagnosing the issue. List the specific parts of the stack trace that are incomplete or unclear, and explain why each missing part is important for understanding the error. Additionally, suggest any additional context or details that would be helpful to fully resolve the issue.

Please analyze the full context of the error stack trace provided. Include details about the specific error messages, the sequence of events leading to the error, and any relevant code snippets that may help in understanding the issue. Additionally, summarize potential causes of the error and suggest steps for resolution. Your response should be structured in a clear format with headings for each section, and aim for a length of at least 150 words.

Please verify that the full error stack trace is properly integrated into the diagnostic process for [APPLICATION NAME]. Check if all relevant error details are captured and displayed correctly. If there are any discrepancies or issues, document them clearly, including the specific errors encountered and any steps taken to troubleshoot. Provide a summary of your findings and any recommendations for improvement.

Create a new rule for CLAUDE.md that ensures full error stack traces are always read. The rule should specify the conditions under which the full stack traces must be captured, including any relevant error types or scenarios. Additionally, outline the consequences of not adhering to this rule and provide an example of how to implement it in a code snippet. Ensure the rule is clear, concise, and easy to follow for developers.

Help me develop a comprehensive checklist for opening sessions that ensures a full error stack trace is read and understood. The checklist should include specific items such as verifying the error message format, checking for any missing components in the stack trace, confirming the environment settings, and ensuring that all relevant logs are reviewed. Additionally, include steps for documenting findings and any follow-up actions that may be necessary. Format the checklist in a clear, numbered list for easy reference.

Please provide a code comment that reminds developers to check the full error stack trace when handling exceptions. The comment should be clear and concise, emphasizing the importance of reviewing the entire stack trace for effective debugging. Include specific examples of scenarios where overlooking the stack trace could lead to issues. Format the comment in a way that can be easily integrated into the codebase, ensuring it is informative and encourages best practices.

Develop a comprehensive naming convention for error logs that enhances full stack trace visibility. The convention should include specific guidelines on how to format error log names, incorporating elements such as the date, time, error type, and relevant identifiers. Additionally, explain the rationale behind each component of the naming structure and provide examples of well-formed log names. Ensure that the convention promotes clarity and consistency, making it easier for developers to identify and troubleshoot issues effectively.

Design a project guard that monitors error handling within a software application. The guard should alert developers whenever full error stack traces are not read or logged properly. Describe its functionality in detail, including how it detects incomplete error handling, the types of notifications it sends (e.g., email, dashboard alert), and the criteria for triggering an alert. Additionally, outline how it integrates with existing logging systems and any configuration options available for customization. Provide a summary of potential benefits this guard could bring to the development process, such as improved debugging efficiency and reduced downtime.