AI Prompts for Tracking Multi-File Changes Effectively

Please provide the last output generated for the function located in [FILE] at line [LINE]. Compare this output to the expected function signature: [EXPECTED SIGNATURE]. Identify and highlight any discrepancies between the two, explaining how they differ and the potential impact on functionality.

Please analyze the following last build error message from the build tab: [LAST BUILD ERROR MESSAGE]. Identify the specific files that were involved in this failure and provide a brief explanation of how each file contributed to the error. Format your response in a clear list, detailing the error message and the associated files.

Please provide your interpretation of my original instruction regarding the changes I wanted in [SPECIFIC FILE]. Include any specific details or aspects that you believe are important for understanding my request. After your interpretation, summarize any potential misunderstandings that could arise from my instructions and suggest how we can address them to ensure clarity moving forward.

Compare the expected behavior of the function in [FILE] at [LINE] with the actual implementation. Clearly outline what the expected output should be and detail the output that was actually produced. Additionally, identify any discrepancies between the expected and actual behavior, providing insights into potential reasons for these differences.

Identify the specific rule or constraint that was violated when changes were made to [SPECIFIC FILE]. Please provide the exact clause from the relevant documentation that was not adhered to, and explain how the changes deviated from this rule. Additionally, suggest potential ways to rectify the situation to ensure compliance moving forward.

Please revert the function signature in the file located at [FILE] on line [LINE]. The original signature is [PASTE ORIGINAL SIGNATURE], and the changed signature is [PASTE CHANGED SIGNATURE]. Before applying the change, provide me with a diff that highlights the modifications made to the signature.

Rewrite the function located in [FILE] at line [LINE] to comply with the following constraints: [LIST CONSTRAINTS]. Provide a detailed explanation of how each change adheres to these constraints and ensure that the final output maintains the original functionality of the function while implementing the specified modifications. Format the response to clearly differentiate between the original code and the revised version.

In [FILE], review the current import statements and ensure they are scoped correctly according to the following requirements: [LIST REQUIRED IMPORTS]. Please add only the specified imports without making any alterations to the existing code structure. Provide a summary of the changes made and confirm that the functionality remains intact.

Please review the function located in [FILE] at [LINE] and ensure it adheres to the specified formatting guidelines: [SPECIFIC FORMAT]. Make any necessary adjustments to achieve consistency in the formatting. After applying the changes, provide a summary of the modifications made and confirm that the function now meets the required standards.

Identify any missing dependencies in the file [FILE] that are crucial for the project to run smoothly. Compare the existing dependencies against the expected list: [LIST DEPENDENCIES]. For any dependencies that are absent, add them to the file and provide a brief explanation of why each is necessary to prevent potential runtime errors.

Please run a test for the function located in [FILE] at [LINE]. Confirm whether it behaves as expected by providing detailed results of the test, including any errors encountered, the output generated, and whether it meets the intended functionality. Format your response in a clear report structure, highlighting key findings and any recommendations for improvements if necessary.

Please provide a detailed diff of the changes made to [FILE]. Highlight all alterations, including additions, deletions, and modifications. Additionally, summarize the key changes and confirm that all necessary edits were applied correctly, ensuring clarity on the impact of each change.

Replay the original scenario that caused the failure in [FILE]. Please provide a detailed account of the steps taken during the replay, including any error messages encountered and the behavior of the system. Confirm whether the issue persists after the recent changes, and summarize any differences observed compared to the initial failure.

Please analyze the function in [FILE] for any potential regressions by checking edge cases that may have been affected by recent changes. Provide a detailed report that includes a list of identified edge cases, a description of how each case could lead to a regression, and any recommendations for testing or fixing these issues. Ensure that your findings are well-structured and clearly articulated for easy understanding.

Please verify the output state of [SPECIFIC FILE] after the recent changes have been made. Check if the output matches the expected result of [EXPECTED OUTPUT]. If there are discrepancies, provide a detailed explanation of what differs and suggest possible reasons for the mismatch. Format your response in a clear and structured manner, outlining each point for easy reference.

Please create a session-opening constraint for the project titled 'Multi-File Change Tracking Constraint.' The constraint should state: 'Before any multi-file change, verify that all changes are tracked across files. If any file is unchanged, stop and alert the user before continuing. Never proceed without confirming all files are updated.' Format this as a clear and concise guideline that can be easily referenced during the development process.

Please create a conversation-starter template for confirming changes across multiple files. The template should follow this structure: "Before finalizing changes, confirm that the following files have been updated: [LIST FILES]. If any files are not updated, please stop the process and notify the user immediately." Ensure the template is clear and concise for effective communication.

Please create a code comment guard in [FILE] that includes the following message: 'Ensure this function is updated in all related files. If changes are made here, verify corresponding updates in [LIST RELATED FILES].' This comment should be placed at the beginning of the function to serve as a reminder for future edits. Additionally, provide a brief explanation of why maintaining consistency across related files is important for code integrity.

Create a project convention message for developers regarding file updates. The message should state: 'All developers must confirm that changes in multiple files are tracked and updated accordingly.' Additionally, provide a detailed checklist for developers to follow to ensure compliance. Format the checklist as bullet points, including items such as verifying file versions, documenting changes, and communicating updates to the team.

Please create a self-check request for the deployment agent to ensure that all files have been updated according to the most recent changes. The request should include a verification process that checks each file for discrepancies. If any discrepancies are found, the agent should alert the user immediately with a detailed report of the files that did not meet the update criteria.