AI Prompts for Preventing Reverted Code Changes

Please quote the exact output produced by the function in [FILE] at line [LINE]. Then, compare this output to the expected output based on the approved changes. Highlight any discrepancies between the produced output and the required output, and provide a brief explanation of the potential reasons for these differences.

Please analyze the last deployment log from the console: [DEPLOYMENT LOG]. Identify any specific indications or error messages that explain why the approved changes were reverted or ignored during the deployment process. Provide a summary of your findings, highlighting the key issues and any recommendations for resolving them.

Please interpret the last instruction I provided regarding the code changes. Clearly explain your understanding of the instruction, including the key points and any specific actions that were implied. This will help us identify any potential miscommunication before proceeding with any changes.

Create a structured comparison table that outlines the expected behavior of the code changes against the actual behavior observed after the last deployment. For each change, include a detailed description of the expected outcome in the [EXPECTED OUTCOME] column and the actual outcome in the [ACTUAL OUTCOME] column. Ensure the table is clear and easy to read, and provide a brief summary of any discrepancies found between the expected and actual behaviors.

Please analyze the recent deployment and identify the specific rule or constraint that was violated. Quote the exact clause from the approved changes that pertains to this violation. Provide a detailed explanation of how this rule was breached and any potential implications for future deployments.

Please revert the function signature at [FILE]:[LINE] to its original form, which is [PASTE]. Before applying the change, provide me with a diff that highlights the differences between the current signature and the original one. Ensure that only the signature is reverted and no other changes are made.

Rewrite the component in [FILE] to incorporate explicit constraints that prevent Replit from reverting changes. Clearly define these constraints to ensure they enforce the approved behavior effectively. Additionally, provide a brief explanation of how each constraint contributes to maintaining the intended functionality and stability of the component.

Please make a scoped change to the [SPECIFIC FUNCTION] in [FILE]. Focus on modifying only the necessary lines to ensure that no other approved changes are unintentionally reverted. After making the changes, provide a brief summary of what was modified and the reasoning behind each change, ensuring clarity on how the modifications maintain the integrity of the overall code.

Enforce a specific code format in [FILE] to prevent Replit from misinterpreting changes. Please outline the exact formatting rules that must be followed, including indentation style, line length limits, and any specific syntax requirements. Additionally, provide examples of correctly formatted code snippets to illustrate these rules clearly.

Review the imports in [FILE] to identify any discrepancies. Confirm that all dependencies are correctly imported and that there are no missing or incorrect references that could lead to issues with reverting changes. Provide a detailed list of any discrepancies found, along with suggested corrections for each import.

Please run a test on the function in [FILE] to verify that it behaves as expected after the recent changes. Ensure that the output aligns with the approved specifications, and provide a summary of the test results, including any discrepancies or confirmations of expected behavior. Additionally, outline any further actions needed if the output does not match the specifications.

Please provide the diff of the last changes made to [FILE]. Ensure that all approved changes are included and highlight any areas where unintended reversion may have occurred. Present the output in a clear format that distinguishes between added, removed, and unchanged lines for easy review.

Please replay the last scenario where the code changes were reverted. Verify that the changes now persist by comparing the output with the approved version. Provide a detailed report on any discrepancies found, including specific examples of how the output aligns or does not align with the approved version.

Please verify the handling of edge cases related to the changes made in [FILE]. Identify specific edge cases that could potentially trigger a reversion and explain how each case is currently managed. Provide a summary of your findings, including any necessary adjustments or confirmations that the changes are robust against these edge cases.

Please confirm the current output state for [FILE]. Check to ensure that it accurately reflects the approved changes and verify that there are no indications of any reversion to previous states. Provide a summary of your findings, including any discrepancies or confirmations of the output state.

Please create a session-opening constraint for the project titled 'Deployment Integrity Check'. The constraint should follow this format: 'Before any deployment step, verify that all approved changes in [FILE] are present. If any changes are missing, stop and alert the user before continuing. Never deploy without confirming all changes are intact.' Ensure the language is clear and concise for easy implementation.

Create a conversation-starter template for confirming code changes before proceeding. The template should prompt the user with the following message: "Before proceeding, confirm that the following changes in [FILE] have been approved: [LIST CHANGES]. If not, please halt and review the changes." Ensure the template is clear and encourages careful review of the changes listed.

Please insert a code comment guard in [FILE] that reads: 'DO NOT REVERT: These changes have been explicitly approved. Any reversion will require a review and approval process.' Ensure that this comment is placed at the top of the file for visibility and clarity. Additionally, provide a brief explanation of the importance of this guard in maintaining code integrity and preventing unauthorized changes.

Please draft a project convention message for the use-case of [USE-CASE] that clearly states the following: 'All code changes must be verified against the approved list before deployment. Any discrepancies must be resolved prior to proceeding.' Ensure the message is formal and emphasizes the importance of adherence to this verification process. Include a brief explanation of the consequences of failing to follow this convention.

Please create a self-check request for the agent to execute before deployment. The request should ensure that all changes in [FILE] match the approved list. If any discrepancies are detected, the agent should alert the user immediately with a detailed report of the differences found.