AI Prompts for Enforcing Consistent Naming Conventions

Please scan the current code file and identify all naming conventions used throughout. Specifically, list every instance of camelCase, snake_case, and PascalCase that you encounter. For each naming convention, provide a brief explanation of its usage in the file, including the total count of each type and examples of where they appear. Format your response in a clear, organized manner, with sections for each naming convention.

Please analyze the content of my CLAUDE.md file provided below: [PASTE CONTENT]. Check for compliance with the naming conventions outlined within the document. Specifically, identify any inconsistencies or deviations from the established conventions, and provide a detailed report highlighting the issues found. Additionally, suggest corrections or improvements to ensure full compliance with the naming standards.

Please analyze the project and identify any files that do not comply with the naming conventions specified in the CLAUDE.md file. Provide a detailed list of these non-compliant files, including their paths and a brief explanation of how each file deviates from the established naming conventions. Additionally, suggest possible corrections for each file to ensure compliance. Format the output as a structured report that is easy to review.

Identify all instances in the current code file where naming conventions are inconsistent. For each inconsistency, provide the line number along with a brief example of the mixed naming conventions. Additionally, categorize the types of naming conventions used (e.g., camelCase, snake_case, PascalCase) and suggest a consistent naming convention that could be applied throughout the file. Format the output in a clear list for easy reference.

Analyze the current file for naming convention issues and provide a detailed summary. Include the specific types of naming inconsistencies you find, such as variable names, function names, and class names, along with the number of occurrences for each type. Additionally, highlight any patterns or common mistakes that may be contributing to these issues. Format the summary in a clear, organized manner, using bullet points for easy readability.

Please convert all identifiers in the provided code file to camelCase format. Ensure that the conversion adheres to the naming conventions outlined in the CLAUDE.md file. After making the changes, provide a summary of the modifications made, including the original names and their corresponding camelCase versions. Additionally, highlight any potential issues or conflicts that may arise from these changes.

Please convert all identifiers in the current code file to snake_case format. Ensure that all variable names, function names, and class names are updated accordingly. Reference the naming conventions outlined in the CLAUDE.md file to maintain consistency throughout the code. Provide the updated code in a clear format, highlighting the changes made for easy review.

Please convert all identifiers in the current file to PascalCase. Ensure that each identifier follows the PascalCase naming convention, where the first letter of each word is capitalized and there are no spaces or underscores. Additionally, provide a summary of the changes made, including any identifiers that were particularly challenging to convert and how you resolved those issues. Format the output as a list of the original identifiers alongside their converted versions for clarity.

Please review the identifiers in the current code file and apply the naming conventions specified in the CLAUDE.md file. Ensure that all variable names, function names, class names, and any other identifiers are consistent with the guidelines outlined in the document. Provide a summary of the changes made, highlighting any identifiers that were renamed and the reasons for those changes. Additionally, check for any potential conflicts or issues that may arise from these renaming adjustments.

Refactor the entire codebase to ensure that all files and variables comply with the naming conventions specified in the [NAMING_CONVENTION_FILE]. Provide a detailed report of all changes made, including a summary of the original naming and the new naming for each file and variable. Ensure consistency across the codebase, and highlight any areas where the naming conventions were not followed. Additionally, include a brief explanation of why adhering to these conventions is important for code readability and maintainability.

Please review the current file and confirm that all identifiers adhere to the specified naming convention. Provide a detailed report highlighting any identifiers that do not comply, including their current names and the suggested compliant names. Additionally, summarize the overall compliance status of the file, indicating the percentage of identifiers that meet the naming standards. If any issues are found, suggest steps to rectify them.

Please run a series of tests to verify that the recent changes to the naming conventions have not introduced any errors in the codebase. Focus on identifying any inconsistencies or issues that may have arisen due to the updates. Provide a detailed report of the results, including any errors found, the specific areas of the code affected, and recommendations for addressing any issues. Ensure that the tests cover all relevant components impacted by the naming changes.

Please generate a comprehensive report on the current state of naming conventions across the codebase. The report should include an analysis of naming consistency for variables, functions, classes, and files. Identify any inconsistencies or deviations from established naming standards, and provide recommendations for improvement. Additionally, include examples of both compliant and non-compliant naming instances, and suggest best practices for maintaining consistent naming conventions moving forward. Format the report in a clear and organized manner, with sections for each type of naming convention.

Please scan the codebase for any instances of incorrect naming conventions. Provide a detailed report that includes the specific lines of code where these inconsistencies occur, along with suggestions for correcting them. Additionally, summarize the overall impact of these naming issues on code readability and maintainability, and recommend best practices for naming conventions moving forward. Ensure the report is clear and structured for easy reference.

Please review the entire codebase and confirm that it adheres to the naming conventions outlined in the CLAUDE.md file. Provide a detailed report highlighting any inconsistencies or deviations from the specified conventions. For each identified issue, include the file name, line number, and a suggested correction to ensure compliance. Additionally, summarize the overall adherence level of the codebase and any patterns observed in the naming conventions.

Please draft a new naming convention rule for the CLAUDE.md file to ensure consistency across our codebase. The rule should include specific guidelines on how to name variables, functions, classes, and files, along with examples of both correct and incorrect naming practices. Additionally, outline the rationale behind these conventions and how they contribute to better code readability and maintainability. Ensure that the rule is clear, concise, and easy for all team members to understand and follow.

Please add a comment at the top of each file that clearly specifies the naming convention being used throughout the code. The comment should include details such as the format for variable names, function names, class names, and any other relevant naming rules that apply. Additionally, provide examples of correctly named variables and functions according to the specified conventions. Ensure that the comment is concise yet informative, making it easy for other developers to understand and follow the naming standards in the codebase.

Create a comprehensive checklist for developers to use before committing code to ensure consistent naming conventions are followed. The checklist should include specific guidelines for naming variables, functions, classes, and files, along with examples of both correct and incorrect naming practices. Additionally, include points on how to handle abbreviations, acronyms, and special characters in names. Format the checklist in a clear, easy-to-follow manner, with sections for each type of naming convention and a brief explanation of the importance of consistency in code readability and maintainability.

Please draft a comprehensive set of naming guidelines for our project documentation. The guidelines should cover best practices for naming variables, functions, classes, and files, ensuring consistency throughout the codebase. Include specific examples of acceptable naming conventions, such as camelCase, snake_case, and PascalCase, along with explanations of when to use each style. Additionally, outline any project-specific rules or exceptions that should be followed to maintain clarity and readability in the code. Aim for a document that is clear, structured, and easy to reference for all team members.

Create a guard mechanism that integrates into the build process to identify and catch any deviations from the specified naming conventions. The guard should analyze the codebase for consistency in naming across variables, functions, and classes, and provide detailed feedback on any discrepancies found. Include a report format that lists the affected areas, suggests corrections, and outlines the importance of adhering to naming conventions for maintainability and readability. Ensure that the guard can be easily configured to accommodate different naming standards as needed.