AI Prompts for Tracking Multi-File Edits Effectively

Please quote the last output generated regarding file changes. Identify the files that Bolt claims to have modified and compare them with the files that were actually required to be changed. Highlight any discrepancies between these two lists and provide a brief explanation of the potential impact of these discrepancies on the overall project.

Please analyze the change log generated by Bolt after my last multi-file edit. I need you to identify how many files were reported as changed and compare this number to my intended changes. Highlight any discrepancies and specify which modifications are missing, providing a clear summary of your findings.

Please summarize your interpretation of my last instruction about the multi-file edits before making any further changes. Include any key points or potential misunderstandings you might have identified. This will ensure we are aligned and can proceed effectively.

Please provide a detailed comparison of the expected file changes versus the actual changes reported by Bolt. For each file, list the expected changes and clearly indicate which changes were not processed correctly. Format the output in a table with columns for 'File Name', 'Expected Changes', and 'Actual Changes', and include a summary of any patterns or common issues observed in the discrepancies.

Please identify and quote the specific rule or constraint that was violated in the change tracking process for the use-case of [USE-CASE NAME]. Specify the exact clause from the documentation that outlines how changes should be tracked across multiple files. Additionally, provide an explanation of why this violation occurred and suggest potential solutions to prevent it in the future.

Please revert the changes made to the function in [FILE] at [LINE]. The original function is as follows: [PASTE]. The modified version is: [PASTE]. Before applying the revert, provide me with a diff comparison that highlights the differences between the original and modified functions.

Rewrite the change tracking logic in [FILE]. Ensure that the new logic explicitly maintains a record of all modified files during multi-file edits. Please provide the updated code snippet along with a brief explanation of how the changes improve tracking accuracy and performance.

Confirm that the changes made in [FILE] are only scoped to the intended modifications. Please provide a detailed list of all files that were modified during this process. Additionally, verify and summarize any unintended changes that may have occurred, ensuring that only the desired modifications are present.

Please enforce a specific format for change logs in your project. Ensure that all changes are documented using the following structure: 'File: [FILENAME], Changes: [DETAILS]'. Provide a summary of how you will monitor compliance with this format and any steps you will take to address inconsistencies.

Please review the dependencies in [FILE] and verify that all imports are accurately referenced. Identify and list any imports that have been added but are not confirmed to exist within the project. Additionally, provide suggestions on how to resolve any discrepancies found, including steps to ensure all necessary dependencies are properly included.

Please conduct a test to verify the change tracking functionality across multiple files. Ensure that all intended changes are accurately reflected in the output logs. Provide a detailed report that includes any discrepancies found, a summary of the changes tracked, and suggestions for improvements if issues are identified.

Please provide a detailed diff of the recent changes made in the project titled [PROJECT NAME]. Ensure that the output highlights all modifications clearly, indicating which lines were added, removed, or altered. Additionally, confirm that the diff accurately reflects the intended changes without including any extraneous modifications. Format the results in a clear and organized manner for easy review.

Replay the last multi-file edit scenario that caused tracking issues. Provide a detailed analysis of the output to confirm whether all changes are now being tracked correctly. Include any discrepancies observed during the replay and suggest potential solutions to address any remaining tracking issues.

Identify an edge case in the change tracking functionality of the system where it might fail. Please provide a detailed analysis of this edge case, including the specific conditions under which the failure occurs, and verify if the latest implementation addresses this issue effectively. Include any relevant test cases or scenarios that demonstrate the resolution of this edge case.

Confirm the state of [SPECIFIC FILE] after the recent changes have been made. Please provide a detailed comparison between the previous and current versions, highlighting any discrepancies and confirming that the expected modifications are present. Additionally, ensure that Bolt retains the necessary context for these changes and summarize any relevant observations in a structured format.

Please create a session-opening constraint for a project focused on change tracking verification. The constraint should be formatted as follows: 'Before any multi-file edit, verify that all intended files are listed for modification. If any files are missing, stop and alert the user before continuing.' Ensure that the wording is clear and precise, and provide any additional context or considerations that may be relevant for implementation.

Please create a change log documentation template that follows this specific format: 'Change Log: [DATE], Files Modified: [LIST OF FILES], Changes: [DESCRIPTION OF CHANGES].' Ensure that the template includes clear instructions on how to fill in each section, and provide an example entry to illustrate proper usage. Additionally, suggest best practices for maintaining consistency in documenting changes over time.

Please draft a confirmation message for users who are about to make edits to multiple files. The message should clearly state: "You are about to modify the following files: [LIST]. Please confirm these changes before proceeding to ensure accuracy." Ensure the tone is professional and encourages users to double-check their edits for correctness.

Please create a detailed reminder for best practices in change tracking. Include specific guidelines such as: "Always document changes in the following format: [FORMAT]. Ensure all modifications are verified before deployment." Additionally, provide examples of common mistakes to avoid and tips for maintaining accurate records throughout the development process. Format the response as a checklist that can be easily referenced.

Please create a self-check request for the agent to ensure accurate change tracking. The request should include the following steps: First, confirm that all modified files are accurately tracked and listed. Next, if any discrepancies are found, the process should be halted immediately. Format the output as a checklist that the agent can follow before proceeding with any changes.