AI Prompts for Detect Function Signature Changes

Quote the original function signature from [FILE] at line [LINE] and provide the modified function signature you generated. Additionally, identify the specific line where the change occurred, and confirm that both signatures align with the expected format. Present your findings in a clear comparison format, highlighting any differences between the two signatures.

Please provide the exact error message from the console that indicates a function signature issue. Analyze this message to identify which specific function calls are failing as a result of the signature change. Additionally, summarize the implications of these failures on the overall functionality of the API and suggest potential solutions to resolve the issues.

Please interpret the original instruction regarding the function signature for the [FUNCTION NAME]. Clearly state your understanding of what the expected signature should be, including the parameters and return type. Additionally, explain how this expected signature relates to the current implementation, highlighting any discrepancies or areas for improvement. Provide your response in a structured format, including a comparison between the expected and current signatures.

Compare the expected function signature with the actual signature currently implemented for the [API NAME]. Clearly outline the expected parameters, including their types and any default values, as well as the expected return type. Additionally, provide a detailed analysis of any discrepancies between the expected and actual signatures, and suggest necessary modifications to align them. Format the output in a table for clarity.

Please identify the specific rule or constraint that was violated by the signature change in the API contract. Quote the exact clause that outlines the expected signature format, and provide an explanation of why this violation is significant. Additionally, suggest potential solutions or adjustments that could be made to rectify the issue.

Please revert the function signature at [FILE]:[LINE] to its original form. The original signature is: [PASTE]. The modified signature is: [PASTE]. Before applying the change, provide a diff that highlights the differences between the original and modified signatures.

Rewrite the function located at [FILE] on line [LINE] to ensure it strictly adheres to the expected signature: [EXPECTED SIGNATURE]. Additionally, verify that all references to this function throughout the codebase are updated accordingly to reflect the new signature. Provide a summary of the changes made and any potential impacts on the surrounding code.

Please update all calls to the function located at [FILE]:[LINE] to ensure they match the expected signature of [EXPECTED SIGNATURE]. Focus on modifying only the relevant files to maintain consistency across the codebase. After making the changes, provide a summary of the modifications made and any potential impacts on related functions.

Check the function signature at [FILE] on line [LINE] against the expected format of [EXPECTED FORMAT]. If the signature does not conform to this format, please correct it and provide the updated code snippet. Additionally, include a brief explanation of the changes made to ensure clarity on how the signature was adjusted.

Verify that all import statements in the file located at [FILE] on line [LINE] correctly reference the updated function signature. If you find any outdated imports, please update them to align with the expected signature. Additionally, provide a brief summary of the changes made and any potential impact these corrections may have on the overall functionality of the code.

Please run the test suite for the function calls located at [FILE]:[LINE]. Ensure that all tests pass successfully and verify that there are no signature-related errors. Provide a summary of the test results, including any errors encountered and suggestions for resolving them if applicable.

Please provide a detailed comparison of the changes made to the function located at [FILE]:[LINE]. Highlight the differences in the code, confirm that the function signature aligns with the expected format, and ensure that all references to this function throughout the codebase have been updated accordingly. Present the findings in a structured format, including a summary of the changes and any potential impacts on the overall functionality.

Replay the original scenario that resulted in the function signature error for the [API NAME]. Provide a detailed account of the steps taken to reproduce the issue, including any relevant input data and configurations. After replaying the scenario, confirm whether the error persists and describe the application's behavior, noting any changes or improvements observed in its functionality.

Identify and test edge cases related to the function at [FILE]:[LINE]. Please provide a detailed report on each edge case, including the expected behavior, the actual behavior observed during testing, and any discrepancies found. Additionally, suggest any necessary changes to ensure that all edge cases are handled correctly without introducing new signature issues. Format the report with clear headings for each edge case tested.

Please verify the output state of the function located at [FILE]:[LINE] after implementing the recent changes. Check that it returns the expected results and does not produce any errors. Provide a summary of your findings, including any discrepancies or issues encountered during the verification process.

Draft a session-opening constraint for the project titled 'Function Signature Consistency Check.' Use the following structure: 'Before any function signature change, verify that all calling files are updated accordingly. If [TRIGGER] occurs, stop and [ACTION] before continuing. Never deploy without confirming signature consistency.' Ensure that the constraint is clear and actionable, providing specific examples of potential triggers and actions that should be taken.

Please create a validation template for function calls that includes the following instructions: For every function signature change, ensure that all instances in [SPECIFIC FILES] are updated accordingly. If any outdated instances are found, list them clearly and request confirmation from the user before proceeding with any further actions. Format the output as a checklist that can be easily followed.

Draft a project specification message for the team regarding the notification process for changes in function signatures. The message should clearly state that the team must be notified whenever a function signature is altered. Additionally, include a detailed checklist that outlines the steps to ensure all dependent files are reviewed and updated accordingly. The checklist should cover aspects such as identifying affected files, updating documentation, and verifying functionality after changes.

Please create a naming convention message for enforcing function signature formats. The message should state: "All function signatures must follow the format [EXPECTED FORMAT]. Any deviation from this format must be documented and approved before implementation." Ensure the message is clear and emphasizes the importance of adherence to this rule for maintaining code quality and consistency.

Generate a self-check request for the use-case of [USE-CASE] at the stage of [STAGE]. The request should include the instruction: 'Before finalizing any changes, confirm that all function signatures are consistent across the project.' Additionally, provide a detailed list of any discrepancies found and outline steps to resolve them before proceeding with the changes.