AI Prompts for Identifying Shell Command Failures

Please provide the exact output of the last shell command you executed that failed. Include the command you ran and the corresponding error message that was returned. This information will assist in diagnosing the issue effectively. Format your response with the command on one line and the error message on the next line for clarity.

Please provide the exact error message from the build tab that occurred during your last deployment attempt. I will analyze this message to identify the specific issues causing the failure. Additionally, include any relevant context about the deployment process or changes made prior to the error to help with the diagnosis.

Please provide your interpretation of my original instruction regarding the shell command before retrying the last command. Clearly outline what you understood and any potential areas where miscommunication may have occurred. This will help us diagnose the issue effectively and ensure we are aligned on the expected outcome.

Compare the expected behavior of the last shell command executed in Replit with the actual outcome. Clearly outline what the command was intended to accomplish, detailing the expected results, and then describe what actually occurred, including any error messages or unexpected behavior. Format your response in a table with two columns: one for "Expected Behavior" and another for "Actual Behavior.

Identify the specific rule or constraint that was violated by the last shell command executed in the terminal. Provide a detailed explanation of the command that caused the violation, and quote the exact clause from the documentation that outlines this rule. Additionally, suggest potential corrections or alternative commands that could be used to comply with the identified rule.

Identify the incorrect shell command syntax located at [FILE]:[LINE]. The original command is: [PASTE]. Analyze the command for errors and provide a corrected version. Please present the corrected command clearly and indicate what changes were made to improve the syntax.

Rewrite the following shell command to include an explicit check for the environment variables. Use the format: 'if [CONDITION] then [COMMAND] else [ERROR HANDLING]'. The command to rewrite is: [ORIGINAL COMMAND]. Please provide the updated command with the necessary checks and error handling included.

Modify the command execution in [FILE] to ensure it only runs in the correct environment. The current command is: [PASTE]. Please provide a detailed explanation of the changes made to the command, including any potential issues that may arise from the modification and how to address them. Ensure that the final command is clearly presented and formatted for easy implementation.

Please review the following shell command: [COMMAND]. Ensure that it adheres to the required format: [EXPECTED FORMAT]. If the command does not comply, adjust it accordingly and provide the corrected version along with a brief explanation of the changes made to ensure compliance.

Before executing the shell command, please verify that all necessary dependencies are installed. List the required dependencies as [DEPENDENCY 1], [DEPENDENCY 2], and [DEPENDENCY 3]. For each dependency, confirm its installation status and provide a brief explanation of how to install any that are missing.

Please execute the corrected shell command: [CORRECTED SHELL COMMAND]. After running the command, provide the output in a structured format, including any error messages if they occur. Additionally, confirm whether the command executed successfully and describe any issues encountered during the process.

Please provide a detailed comparison of the changes made to the shell command in [FILE]. Include a side-by-side view of the original and modified commands, highlighting any modifications or deletions made. Additionally, explain the significance of each change and how it affects the overall functionality of the command.

Replay the original scenario that caused the shell command to fail in [PROGRAM NAME] on [PLATFORM]. Provide a detailed account of the steps taken, including the exact commands used and any error messages received. Confirm whether the issue persists or if it has been resolved, and summarize any changes made since the original failure.

Test the shell command for the use case of [REPLIT WRONG TERMINAL COMMANDS] against known edge cases that previously caused failures. Identify each edge case and confirm whether it now executes correctly without errors. Provide a detailed report on the results, including any remaining issues and suggestions for further improvements.

Please confirm the output state of [SPECIFIC FILE] after executing the shell command [COMMAND]. Detail the changes that should be reflected in the output and explain how they align with the expected results. Additionally, provide any discrepancies you observe and suggest possible reasons for these differences.

Before executing any shell command, verify [SPECIFIC CHECK 1] and [SPECIFIC CHECK 2]. If [TRIGGER] occurs, stop and [ACTION] before continuing. Never execute without [CONSTRAINT].

Please create a project convention message that outlines guidelines for executing shell commands. The message should begin with the statement: "All shell commands must adhere to the following guidelines:" and then include a detailed list of specific guidelines in bullet point format. Ensure that the guidelines cover best practices, common pitfalls to avoid, and any necessary safety precautions. Provide the final text in a format that can be easily copied and pasted.

Please create a self-check request template that verifies environment variables before executing any command. The template should include a check for the following variables: [VARIABLE 1] and [VARIABLE 2]. If either variable is not set, the template should log an error message and halt execution. Format the output as a clear, paste-ready code snippet that can be easily integrated into a script.

Draft a conversation-starter template that outlines a strategy for handling command errors. Use the following structure: 'If a command fails, log the error and attempt to [RECOVERY ACTION]. Additionally, include a brief explanation of why this recovery action is important and how it can prevent future occurrences of similar errors. Ensure the final output is clear and ready for immediate use.

Before executing any command, please verify that [DEPENDENCY 1] and [DEPENDENCY 2] are installed on the system. If either dependency is missing, log an error message indicating which dependency is not installed. Ensure that the verification process is clearly documented and easy to follow for future reference.