AI Prompts for Prevent Unasked Changes in Code

Quote the last output you generated regarding the function in [FILE]:[LINE]. Please identify and list the specific changes made to this function compared to its original definition. Additionally, analyze and confirm which parts of the changes were not part of the original request, providing a brief explanation for each unrequested change.

Paste the output from the last edit where unasked changes were made: [LAST EDIT OUTPUT]. Analyze this output to identify which files or functions were altered without being mentioned in the task. Provide a detailed list of the changes, including the specific lines of code that were modified and an explanation of how these changes impact the overall functionality of the project. Format the analysis in a clear, structured manner for easy reference.

Please interpret the original instruction provided for the project titled [PROJECT TITLE]. Clearly outline your understanding of the key objectives and requirements stated in the instruction. Additionally, identify any potential areas of ambiguity that could lead to misunderstandings or unintended changes. Present your interpretation in a structured format, including bullet points for clarity, and provide suggestions on how to address any identified ambiguities.

Please provide a detailed comparison of the expected changes versus the actual changes made in the last edit for the project titled [PROJECT NAME]. Clearly outline what was expected based on the task description, including specific elements such as features, functionality, and design aspects. Additionally, highlight any discrepancies between the expected and actual changes, and suggest potential reasons for these differences.

Please identify and quote the specific rule or constraint that was violated in the last edit related to the task description and expected behavior. Provide a clear explanation of how this violation impacts the overall project scope and suggest potential solutions to address the issue. Format your response with the quoted constraint, an analysis of the violation, and your proposed solutions.

Revert the unasked changes made to [FILE] at [LINE]. Identify the specific modifications that were not part of the original task and ensure that only those changes are reverted. Maintain the integrity of the remaining code in the function, and provide a summary of the changes that were reverted.

Rewrite the function located at [FILE] on line [LINE] to ensure it strictly adheres to the original task description. Clearly outline the specific constraints that must be followed in this rewrite, and include only the necessary changes to achieve compliance. Provide a brief explanation of how these changes align with the original requirements.

Please make a scoped change to [FILE] at line [LINE] that aligns with the original task. Clearly explain how this change adheres to the intended scope and detail any potential impacts on surrounding code. Additionally, provide a brief summary of how you ensured that no other parts of the code were affected by this change.

Please review the changes made to [FILE] at [LINE] and ensure they adhere to the specified format outlined in the task description. Identify and highlight any deviations from this format, providing a brief explanation for each deviation. Additionally, suggest how these changes can be corrected to align with the required format.

Please verify the dependencies added in the last edit for the task of [TASK NAME]. List each dependency and provide a brief explanation of its relevance and necessity for the current functionality. Additionally, indicate if any dependencies can be removed or are redundant.

Run a functional test on [FUNCTION] located in [FILE] to verify that it operates correctly after reverting the unasked changes. Please provide a detailed report of the test results, including any discrepancies observed, the expected behavior, and the actual outcomes. Additionally, include any recommendations for further actions if issues are identified.

Please provide a detailed diff of changes made to [FILE] before and after the last edit. Highlight each modification clearly and confirm that only the necessary changes are present. Additionally, summarize any unnecessary alterations that were removed and explain why they were deemed unnecessary.

Replay the original scenario that led to the unasked changes occurring. Analyze the output generated in this scenario and confirm whether it aligns with the expected behavior. Provide a detailed comparison of the current output against the expected results, highlighting any discrepancies or improvements observed.

Please review the function in [FILE] for any edge cases that may have been impacted by the unasked changes. Identify at least three specific edge cases to test, and confirm whether each one works as intended after the changes. Provide a summary of your findings, including any issues encountered and suggestions for further improvements if necessary.

Please confirm the state of [FILE] after the recent changes have been made. I need you to verify that it reflects only the intended modifications without any unasked alterations. Provide a summary of any discrepancies found and suggest steps to rectify them if necessary.

Create a session-opening constraint for the project titled [PROJECT TITLE]. The constraint should state: 'Before making any changes, confirm that all modifications are explicitly mentioned in the task description. If any unasked changes are detected, halt and report them before proceeding.' Ensure the wording is clear and concise to prevent scope creep.

Generate a conversation-starter template that emphasizes the importance of adhering to task specifications. The template should include a clear directive: 'For every task, ensure that only the specified files and functions are altered. If there are any deviations from the task description, report them before proceeding.' Additionally, provide examples of common deviations and how to address them effectively.

Draft a project specification message for the team regarding change verification. The message should clearly state that all changes must be verified against the original task description. Additionally, include that any changes made outside the defined scope must be documented and confirmed with the developer before implementation. Ensure the message is concise and emphasizes the importance of maintaining project integrity.

Please create a naming convention message that clearly states: 'Any function modifications must include a comment detailing the task reference.' Explain the importance of this practice in ensuring clarity on what was requested versus what was changed. Additionally, provide examples of how this can prevent scope creep and unasked changes in future projects. Format your response as a concise guideline that can be easily shared with the team.

Please create a self-check request for changes that an agent can run before applying any modifications. The agent should verify if the proposed changes align with the original task description. If it detects any changes that were not requested, it should stop the process and notify the developer immediately. Format the output as a clear checklist for the agent to follow.