AI Prompts for Diagnose Reverted Code Changes

Please quote the exact output generated in the last session regarding the use-case of v0-reverting-approved-changes. Identify the specific component or function that was reverted and provide a detailed comparison to the version that was approved. Highlight the differences clearly, and format your response in a structured manner that includes sections for the reverted output, the approved version, and a summary of the key differences.

Please provide the output from the last generation that displays the reverted changes. Analyze the differences between this output and the approved code, highlighting specific alterations and explaining why these changes may not align with the approved version. Format your response in a structured manner, detailing each change and its potential impact on the overall code functionality.

Please interpret the original instruction regarding the component or function [COMPONENT/FUNCTION NAME]. Clearly explain your understanding of the instruction and highlight any specific details that may lead to miscommunication. Include potential implications of your interpretation on the changes to be made, and format your response as a structured summary with bullet points for clarity.

Compare the expected behavior of the component you were working on with the actual behavior that was generated after the reversion. Clearly outline the specific functionalities that were lost due to this change. Provide examples of how the expected functionality should work, and detail any discrepancies you observed, including any error messages or unexpected outcomes. Format your response in a structured list for clarity.

Identify the specific design constraint or rule that was violated in the last output related to [USE-CASE]. Please quote the exact clause from your original instruction that was ignored and explain how this violation impacts the overall design. Additionally, suggest a corrective action to ensure compliance with the design constraints moving forward.

Revert the function signature in the file located at [FILE] on line [LINE] to its original form. The original signature is: [PASTE]. The modified signature is: [PASTE]. Please provide a diff of the changes before applying the reversion, and ensure that the body of the function remains untouched.

Rewrite the component located at [FILE]:[LINE] to ensure it adheres to the original design constraints. The rewritten component should match the approved version provided here: [PASTE]. Additionally, please highlight any differences between the original and the revised component, explaining the reasons for those differences.

Restore the functionality of the component located at [FILE] on line [LINE] by modifying only the lines that were previously reverted. Please identify the specific lines that need to be reinstated from the following list: [PASTE]. After making the changes, provide a brief summary of how these modifications will restore the intended functionality.

Please review the component located at [FILE]:[LINE] to ensure it adheres to the correct formatting rules. Compare it against the approved version provided here: [PASTE]. Identify and highlight any deviations from the approved format, and provide suggestions for correcting these inconsistencies.

Please verify the import dependencies in the file [FILE]. Identify any missing or incorrect dependencies and provide a detailed list of these issues. Additionally, suggest the correct imports needed to resolve any discrepancies, ensuring that the final import statements are properly formatted and functional.

Please run a test on the component located at [FILE]:[LINE]. Ensure that it behaves as expected by comparing the output to the approved version. Provide a detailed report of any discrepancies found, including specific examples of the output and how it differs from the approved version.

Display the diff of the changes made to [FILE]. Highlight the lines that were reverted and the lines that were restored. Additionally, provide a brief explanation of why these changes were necessary and how they confirm the fix. Format the output to clearly distinguish between reverted and restored lines for easy review.

Replay the original scenario that caused the reversion issue for the component. Confirm that it now performs correctly by executing the same steps that led to the failure. Document the results of the replay, noting any discrepancies or improvements, and ensure that the component does not revert to its previous state during this process.

Evaluate the edge cases for the component located at [FILE]:[LINE]. Ensure that the recent fix does not introduce any new regressions by testing various scenarios, including both typical and atypical inputs. Document your findings in a structured format, highlighting any issues discovered and suggesting potential solutions or improvements.

Verify the output state of the component located at [FILE]:[LINE]. Check that it aligns with the expected output and confirm that it has not reverted to any previous changes. Provide a detailed comparison of the current output against the expected state, highlighting any discrepancies and their potential impact on functionality.

Please create a reusable prompt template for verifying changes before they are applied. The template should follow this structure: "Before applying any changes, confirm that the following modifications have been approved: [SPECIFIC CHANGES]. If the changes have not been approved, please revert to the last approved state." Ensure the output is clear and easy to follow for future reference.

Generate a component specification snippet for [COMPONENT NAME]. The snippet should clearly state: 'This component must adhere to the following rules: [SPECIFIC RULES]. Any deviation from these rules will initiate a review process prior to implementing any changes.' Ensure the language is precise and formal, suitable for documentation purposes.

Draft a style constraint phrase that enforces design consistency across all components. Use the following format: 'All components must adhere to the design guidelines outlined in [DOCUMENT]. Any modifications that do not comply with these guidelines will be flagged for review and correction.' Ensure the phrase is clear and emphasizes the importance of maintaining design integrity.

Create a configuration note for shadcn/ui that outlines the design constraints that must be adhered to. Specify the following: 'Ensure all components comply with the following design constraints: [SPECIFIC CONSTRAINTS]. If any violations occur, please detail the process for review and approval of those components, including who will be responsible for the review and the criteria they will use to assess compliance.

Create a context-reload prompt to be used at the beginning of each new generation. The prompt should state: 'Before generating new components, please confirm that the previous changes have been approved and are functioning as expected. If they are not, revert to the last stable version.' Ensure the prompt is clear and concise for effective communication.