AI Prompts for Surfacing Full Error Stack

Please provide the complete error stack trace for the last build failure. Make sure to include every line of the stack trace, detailing the sequence of errors and any relevant context that may help in diagnosing the issue. Additionally, highlight any specific error messages or codes that could indicate the root cause of the failure. Format the output clearly, so it is easy to read and analyze.

Please analyze the context of the error I encountered. Provide a detailed breakdown of the error message, including key components from the stack trace that may help identify the root cause. Explain what each part of the stack trace indicates and how it relates to the overall issue. Additionally, suggest potential solutions or troubleshooting steps based on the analysis of the error context.

Please analyze the error stack trace provided and identify any missing information that may be relevant to diagnosing the issue. For each ignored part, explain why it could be significant in understanding the root cause of the error. Additionally, suggest what steps could be taken to gather this missing information and how it might impact the overall diagnosis. Aim for a detailed response that covers all critical elements of the stack trace.

From the full stack trace provided, please identify the root cause of the error. Explain the reasoning behind your determination, detailing the specific lines or messages in the stack trace that led you to this conclusion. Additionally, outline any potential implications of this error on the overall system functionality and suggest possible solutions or next steps to resolve the issue.

Analyze the first line of the error message in the stack trace and compare it with the following lines. Provide a detailed explanation of how the subsequent lines contribute to understanding the root cause of the error. Discuss any patterns, specific error types, or contextual information that may help in diagnosing the issue. Summarize your findings in a structured format, highlighting key insights and recommendations for resolving the error.

Given the full error stack provided, please analyze the information to pinpoint the root cause of the issue. Explain in detail how this root cause contributes to the overall failure, including any relevant context or dependencies that may be involved. Additionally, outline potential solutions or steps that could be taken to resolve the issue and prevent it from occurring in the future. Format your response in a clear and structured manner, with separate sections for the root cause analysis, explanation, and proposed solutions.

Please analyze the root cause of the issue and provide specific code changes that would effectively resolve it. Include a brief explanation of why each change is necessary and how it addresses the identified problem. Additionally, outline any potential impacts these changes may have on the overall functionality of the code. Format your response in a clear, step-by-step manner, ensuring that each recommendation is easy to understand and implement.

Please analyze the current dependencies in my project and evaluate how they might be contributing to the error I am experiencing. Identify specific dependencies that could be causing issues and suggest changes or updates that could mitigate these problems. Additionally, provide a brief explanation of how each suggested change would improve the overall stability and performance of the project. Format your response as a detailed report with actionable recommendations.

Please analyze the situation where the initial fix did not resolve the issue related to [SPECIFIC ERROR OR PROBLEM]. Based on the full error stack, propose at least three alternative solutions that could potentially address the problem. For each solution, provide a brief explanation of how it works, any prerequisites needed for implementation, and the expected outcome. Ensure that the suggestions are practical and relevant to the context of the issue at hand.

Please confirm that the recent fix has effectively addressed the root cause identified in the error stack trace. Provide a detailed analysis of the changes made and explain how they resolve the issue. Include any relevant test results or observations that demonstrate the fix's effectiveness. Additionally, outline any potential implications or further actions that may be necessary to ensure the issue does not recur.

Please execute a new build for the project and confirm that the previous error related to [ERROR DESCRIPTION] no longer occurs. After the build is completed, provide the detailed output logs for verification. Additionally, summarize any changes made since the last build that may have contributed to resolving the issue. Ensure that the output is clear and highlights any relevant information that indicates the error has been resolved.

Please analyze the build process for any silent failures that may have occurred. Provide a detailed report outlining any issues detected, including the nature of the failures, their potential impact on the build, and suggestions for resolving them. Additionally, include any relevant logs or error messages that can help in diagnosing the problems. Ensure that the report is structured clearly, with sections for each identified issue and recommended next steps.

Please verify that all approved changes made to the components in [COMPONENT NAME] are still intact following the recent fix. List each change that was implemented and confirm whether it has been retained or altered. If any changes are missing or modified, provide details on what has changed and suggest potential next steps for resolution. Format your response in a clear, structured manner to facilitate easy review.

Please evaluate the overall stability of the system following the recent fix. Provide a detailed assessment that includes any lingering issues or anomalies that may still be present. Outline the specific areas of the system that were affected by the fix, and note any performance metrics or error logs that indicate ongoing problems. Additionally, suggest any further actions that may be necessary to ensure complete stability and reliability moving forward.

Please verify that the specific error identified as [ERROR NAME] and its root cause, which was [ROOT CAUSE], are no longer present in the system. Provide a detailed report on the steps taken to confirm this, including any relevant logs or metrics that demonstrate the absence of the error. Additionally, outline any changes made to the system that may have contributed to resolving the issue and suggest any further monitoring or testing that should be conducted to ensure the error does not reoccur.

Please draft a new rule for CLAUDE.md that mandates the review of full error stacks for all resolved issues. The rule should include the rationale for its importance, the specific steps that need to be taken to ensure compliance, and any consequences for failing to adhere to this rule. Additionally, provide examples of scenarios where reviewing the full error stack would be critical for preventing future issues. Format the rule clearly with headings and bullet points for easy reference.

Please add a comment in the codebase that emphasizes the importance of reviewing full error stacks when troubleshooting issues. The comment should explain why understanding the complete error context is crucial for effective debugging and preventing similar problems in the future. Include examples of how overlooking parts of the error stack can lead to misdiagnosis and extended downtime. Ensure the comment is clear, concise, and informative, so that future developers can easily grasp its significance.

Create a detailed checklist for session openers that ensures all aspects of full error stack traces are thoroughly considered during the debugging process. Include specific items such as verifying the error message clarity, checking for relevant logs, ensuring all dependencies are accounted for, and confirming that the environment settings are correct. The checklist should be structured in a way that allows for easy tracking of each item, with space for notes or comments on each point. Aim for at least 10 items to cover various scenarios that may arise during debugging.

Propose a detailed naming convention for error logs that emphasizes the importance of reviewing full stack traces. The convention should include specific elements such as the error type, timestamp, and a unique identifier for each log entry. Additionally, provide examples of how this naming convention can be applied in practice, ensuring that it is easy to understand and implement. Explain the benefits of this convention in terms of improving error tracking and facilitating quicker resolution of issues.

Design a project guard that alerts developers when only the first line of an error message is being considered, ensuring that all relevant details are taken into account. The guard should analyze error logs and identify instances where additional context from the error stack is ignored. Provide a detailed outline of the implementation process, including the programming language to be used, the specific conditions that trigger the alert, and how developers will be notified. Additionally, suggest ways to enhance the guard's functionality to improve error handling and debugging efficiency in the project.