AI Prompts for Standardize Naming Conventions Across Files

Identify the specific function name in [FILE] at line [LINE] that does not adhere to the naming convention. Please provide the expected format as [EXPECTED_FORMAT] and compare it to the actual format currently used, which is [ACTUAL_FORMAT]. Format your response clearly, highlighting both the violation and the expected naming rule.

Please analyze the following code snippet for naming inconsistencies: [CODE SNIPPET]. Identify the differences in naming conventions used for variables and functions, and explain how these inconsistencies could impact code readability and maintainability. Provide suggestions for standardizing the naming conventions throughout the code.

Please explain your understanding of the naming conventions required for this project, specifically focusing on the formats that should be used for functions and variables. Include examples of acceptable naming styles, such as camelCase, snake_case, or PascalCase, and describe any guidelines that should be followed to ensure consistency across the codebase. Additionally, outline the potential impact of inconsistent naming conventions on code readability and maintainability.

Please provide a structured comparison of the expected naming conventions versus the actual naming conventions used in [FILE]. Include specific examples for both categories, detailing at least three instances of expected formats and three instances of actual formats. Additionally, explain the implications of these inconsistencies on code readability and maintenance. Format the output as a table for clarity.

Identify the specific naming convention rule that was violated in [FILE]. Please provide the exact clause from the naming convention documentation that defines the expected naming format. Additionally, explain how the violation impacts code readability and maintainability, and suggest a corrected naming format that adheres to the established conventions.

In [FILE]:[LINE], please change the function name from [CURRENT_NAME] to [EXPECTED_NAME] to ensure it aligns with the project's naming conventions. Make sure that the function body remains unchanged and provide a brief explanation of why this change is necessary for consistency. Additionally, confirm that there are no references to the old function name elsewhere in the code.

Rewrite the variable names in [FILE] to adhere to the [SPECIFIC_CONVENTION]. Provide a detailed list of changes, including examples such as transforming [OLD_VARIABLE] into [NEW_VARIABLE]. Additionally, explain the reasoning behind each naming choice to ensure clarity and consistency throughout the code.

Identify all instances of [OLD_FORMAT] in [FILE] and change them to [NEW_FORMAT] to ensure consistency throughout the codebase. Please provide a summary of the changes made, including the number of instances modified and any potential impacts on related code. Confirm that the changes do not affect any unrelated code sections.

Review the contents of [FILE] and identify any instances of inconsistent naming conventions. Enforce a consistent naming format by replacing all occurrences of mixed naming conventions with [SPECIFIC_FORMAT]. Provide a summary of the changes made and ensure that the final output adheres to the specified naming format throughout the file.

Review the import statements in [FILE] and identify any inconsistencies in naming conventions. Ensure that all imported modules adhere to the naming conventions outlined in the project guidelines. Provide a corrected version of the import statements, clearly indicating any changes made for consistency.

Please analyze the contents of [FILE] to verify that all naming conventions are consistent throughout. Identify and list any remaining inconsistencies you find, providing specific examples and suggestions for how to resolve each one. Format your findings in a clear report that highlights the inconsistencies and proposed corrections.

Please provide the diff of changes made to [FILE] after applying the naming convention updates. Ensure that all modifications to the naming formats are clearly highlighted. Additionally, summarize the key changes in a brief report, outlining the impact of these modifications on the overall code consistency.

Replay the original scenario that caused the naming convention issue in [FILE]. Provide a detailed account of the steps taken during the replay, including any relevant logs or outputs that demonstrate the resolution of the issue. Additionally, confirm whether the problem persists or if it has been successfully resolved, and summarize any changes made to prevent future occurrences.

Please analyze the contents of [FILE] for any edge cases where naming conventions may be inconsistent. Identify specific instances where the naming does not adhere to the specified format, and provide a summary of these issues along with recommendations for ensuring uniformity. Format your findings in a clear report, highlighting each inconsistency and suggesting corrective actions.

Please confirm the final state of [FILE] after the recent changes have been made. Review the code to ensure that all functions and variables adhere to the agreed-upon naming conventions. Provide a summary of any inconsistencies found, along with suggested corrections to align with the naming standards.

At the beginning of each session, enforce naming conventions by ensuring all variable and function names adhere to [SPECIFIC_CONVENTION]. If any inconsistencies are detected, halt the process and provide a detailed report of the violations, including the specific names that do not comply and suggestions for correction. Format the report clearly, listing each violation with its corresponding line number and the expected naming convention.

Create a conversation-starter template for discussing naming guidelines. Include a section that prompts users to confirm that all naming conventions in [SPECIFIC_FILE] adhere to [SPECIFIC_CONVENTION] before making any changes. Additionally, provide a checklist of common naming conventions and examples to facilitate the discussion and ensure clarity among team members.

Draft a project specification message that outlines the importance of consistent naming conventions in our codebase. State that all code must adhere to the [SPECIFIC_CONVENTION] for naming functions and variables. Include a reminder for developers to review their code thoroughly for compliance with this standard before submission, and suggest a brief checklist to ensure all naming conventions are followed correctly.

Please create a self-check request for ensuring naming consistency in code. Before finalizing any code, instruct the AI to check that all naming conventions in [SPECIFIC_FILE] adhere to [SPECIFIC_CONVENTION]. Provide a clear checklist format that includes specific examples of correct and incorrect naming conventions to guide the review process.

Create a reminder message that emphasizes the importance of using [SPECIFIC_CONVENTION] for naming functions and variables in all files. The message should encourage developers to check for consistency before deployment. Format the message clearly and concisely, ensuring it can be easily understood and referenced by the team.