AI Prompts for Standardize Naming Conventions in Code

Please analyze the main file for naming convention violations. Quote the exact line where a variable or function does not adhere to the expected naming convention. Clearly identify the specific variable or function that is in violation, and provide a brief explanation of how it deviates from the established naming rules.

Please analyze the following content of my main file for naming conventions: [MAIN FILE CONTENT]. Identify specific examples of inconsistent naming practices, such as variations in capitalization, underscores, or other formatting issues. Provide a summary of the inconsistencies found, along with suggestions for standardizing the naming conventions throughout the file.

Please explain your understanding of the naming conventions required for this project. Include details on specific naming styles (e.g., camelCase, snake_case) and any guidelines for naming variables, functions, and classes. Additionally, provide examples of both correct and incorrect naming practices to illustrate your points.

Please provide a structured comparison of the expected naming conventions versus the actual naming behavior in the main file. For each variable or function, list the expected format and detail how the current implementation deviates from this standard. Include examples for clarity and organize the output in a table format for easy reference.

Please analyze the following code snippet for naming convention violations: [CODE SNIPPET]. Identify the specific naming convention rule that has been violated and quote the exact clause from the project guidelines that outlines the expected format. Present your findings in a structured format, including the violated rule, the relevant code segment, and the guideline reference.

Identify the function definition in the main file that is currently named 'getUserInfo'. Change this function name to 'get_user_info' to adhere to the project's naming convention of using snake_case. Ensure that this change is made only in the function definition and does not affect any other references to the function in the code. After making the change, provide a brief summary of where the function is defined and how it is used in the project.

Please rewrite the variable name 'userAge' to match the snake_case convention, changing it to 'user_age'. Ensure that all instances of 'userAge' in the main file are updated to 'user_age' for consistency. Provide a summary of all changes made, including the locations where the variable was found and updated.

Please update the class name 'UserProfile' to 'user_profile' in the class definition to align with the project's naming convention of using snake_case. Ensure that this change is isolated and does not affect any other parts of the code. After making the change, provide a brief summary of the modification and any potential impacts on the codebase.

Review all variable names in the main file and identify any that do not follow the snake_case naming convention. For each variable found in camelCase or PascalCase, provide the original name and the corrected name in snake_case. Additionally, summarize the total number of changes made and any patterns observed in the naming inconsistencies.

Review the import statements in the main file of the project. Identify any imports that do not adhere to the snake_case naming convention. For each inconsistent import, provide the corrected version and explain why the change is necessary to maintain consistency throughout the codebase. Format your response as a list of corrections with brief justifications.

Please perform a naming convention check on the main file to verify that all variable and function names adhere to the snake_case format. Identify and list any names that do not conform to this standard, providing specific examples of the inconsistencies found. Additionally, suggest how these names can be corrected to meet the snake_case convention.

Display the differences between the main file before and after the changes to verify that all naming conventions have been corrected. Please highlight the specific lines that were modified and provide a summary of the changes made, including the original and updated naming conventions. Format the output clearly, showing the old and new lines side by side for easy comparison.

Please run the application and verify if the previous issues related to naming conventions have been resolved. Specifically, check for any errors or warnings that may arise due to inconsistent naming. Provide a detailed report on the findings, including any remaining issues and suggestions for improvement.

Review the following code for any edge cases where naming conventions may have been overlooked: [CODE SNIPPET]. Specifically, check that all variable names adhere to the snake_case standard. Provide a list of any inconsistencies found, along with suggestions for correcting them to ensure uniformity throughout the code.

Please review the final state of the main file for the project related to [PROJECT NAME]. Verify that all naming conventions are consistent throughout the file. If you find any discrepancies, list them clearly along with suggestions for how to correct each inconsistency. Format your response in a bullet-point list for easy reference.

Before making any code changes, please verify that all variable and function names in the provided code adhere to the snake_case naming convention. If you find any deviations from this convention, stop the process and provide a corrected version of the code with all names adjusted to comply with snake_case. Present the corrected code in a clear format that highlights the changes made.

Create a conversation starter template for discussing code changes that emphasizes the importance of naming conventions. Include a reminder to confirm that naming conventions are being followed, specifically using snake_case for variables and functions. Format this as a structured dialogue prompt that can be used in team meetings, including an introduction, key points to address, and a conclusion to reinforce the standards.

Please create a comment guard for the main file that ensures all variable and function names adhere to the snake_case naming convention. The comment should read: 'TODO: Ensure all variable and function names are in snake_case. Review before finalizing changes.' Include this comment at the top of the main file to remind developers of the naming standard before they submit their changes.

Generate a reminder message for the project titled [PROJECT NAME] that emphasizes the importance of adhering to naming conventions. The message should state: 'All code must follow snake_case for variable and function names. Please review the naming conventions carefully before committing any changes.' Format the message clearly and concisely for easy understanding.

Please create a self-check request for naming compliance before deployment. The request should include a confirmation that all naming conventions adhere to the project standards. Additionally, provide a structured list of any discrepancies found, including the specific names that do not comply with the standards and suggestions for correction. Format the output as a checklist with sections for compliant names and non-compliant names.