AI Prompts for Resolving Naming Convention Conflicts

Analyze the file [FILE_NAME] and identify all the naming conventions present within it. For each convention, provide a clear example along with a brief explanation of its usage and context. Additionally, categorize the naming patterns into groups based on their similarities, such as camelCase, snake_case, or PascalCase. Summarize any inconsistencies you find and suggest best practices for maintaining uniformity in naming conventions throughout the file.

Review the file [FILE_NAME] and identify any variables or functions that do not adhere to the established naming conventions of the project. Provide a detailed list of the violations you find, including the specific names of the variables or functions, the expected naming convention they should follow, and suggestions for how to rename them to comply with the standards. Additionally, summarize the potential impact of these violations on code readability and maintainability. Format your response in a clear and organized manner.

Please scan the file [FILE_NAME] and identify all instances where inconsistent naming conventions are present. For each instance, provide the specific line numbers along with a brief description of the naming conventions used. Additionally, categorize the types of naming conventions found, such as camelCase, snake_case, or PascalCase, and highlight any patterns or common issues that may contribute to the inconsistencies. Format your findings in a clear list for easy reference.

Examine the file [FILE_NAME] and analyze the naming conventions used throughout the document. Identify the dominant naming convention and provide a detailed percentage breakdown of each convention found. Include specific examples of each naming style and explain any patterns or inconsistencies you observe. Additionally, suggest recommendations for standardizing the naming conventions moving forward.

Review the contents of [FILE_NAME] and identify any inconsistent naming conventions present throughout the document. Please provide a detailed list of the inconsistencies you find, including examples of each naming pattern. Additionally, suggest a standardized naming convention that aligns with the project's guidelines, explaining why this convention is preferable and how it can improve clarity and consistency in the project.

Please convert all variable and function names in the file [FILE_NAME] to camelCase format. Review the entire file to ensure that no other naming conventions are present, such as snake_case or PascalCase. Provide a summary of the changes made, including the original names and their corresponding camelCase versions. Ensure that the code remains functional and that all instances of the variables and functions are updated consistently throughout the file.

Transform all identifiers in [FILE_NAME] to snake_case format. Ensure that each identifier adheres to the project's naming conventions and is consistent throughout the file. Provide a summary of the changes made, highlighting any identifiers that were modified and confirming that the final output complies with the project's standards for naming conventions.

Please change all class names in [FILE_NAME] to follow the PascalCase naming convention. After making these changes, verify that the updated names align with the project's established standards for naming conventions. Provide a summary of the changes made and any discrepancies found during the verification process. If there are any names that do not conform to PascalCase, list them along with suggestions for correction.

Please review the code in [FILE_NAME] and standardize all identifiers according to the project's naming convention. Ensure that variable names, function names, and class names are consistent and follow the established guidelines. After making the changes, provide a detailed summary of all modifications, including examples of the original and updated names. Additionally, highlight any areas where the naming convention was not followed and explain the rationale for the changes made.

Please review the naming conventions used in [FILE_NAME] and identify any inconsistencies. Apply the project's preferred naming convention to ensure uniformity throughout the file. Provide a detailed list of all changes made, including the original names and the updated names, along with a brief explanation of why each change was necessary. Aim for clarity and consistency in the final output.

Please review the contents of [FILE_NAME] and verify that all identifiers adhere to the established naming conventions for this project. Create a detailed confirmation report that includes a summary of any inconsistencies found, along with suggestions for corrections. The report should clearly outline which identifiers are compliant and which are not, providing examples for clarity. Additionally, include any recommendations for improving naming consistency in future files.

Please validate the naming conventions applied in [FILE_NAME]. Review the entire document to ensure consistency in naming across all sections, including headings, subheadings, and any referenced terms. Provide a summary of any inconsistencies found, along with suggestions for corrections to align with the established naming standards. Additionally, highlight any areas where the naming conventions are correctly applied to serve as a reference for future use.

Please generate a detailed report for the file named [FILE_NAME] that evaluates the consistency of naming conventions used throughout the document. The report should identify and highlight any inconsistencies or issues found, providing specific examples and suggestions for improvement. Additionally, include a summary section that outlines the overall adherence to naming conventions and any patterns observed in the inconsistencies. Format the report in a clear and organized manner, using bullet points or tables where appropriate to enhance readability.

Please analyze the contents of [FILE_NAME] to ensure that all naming conventions are consistent throughout the document. Identify any instances of mixed naming conventions and provide a detailed report on the findings. Include specific examples of inconsistencies, if any, and suggest a standardized naming convention that could be applied. Finally, conclude with a pass/fail result based on the consistency of the naming conventions.

Please review the contents of [FILE_NAME] to ensure that all naming conventions align with the guidelines specified in the CLAUDE.md document. Provide a detailed analysis of any inconsistencies you find, including examples of non-compliant names and suggestions for correction. Additionally, summarize the overall compliance status of the file, indicating whether it meets the naming conventions or if further adjustments are necessary. Please format your response in a clear and structured manner.

Draft a new naming rule for the document CLAUDE.md to enforce consistent naming conventions across our projects. The rule should clearly define what constitutes acceptable naming practices, including guidelines on naming formats, character usage, and any specific prefixes or suffixes that should be applied. Additionally, include examples of both correct and incorrect naming conventions to illustrate the guidelines. Ensure the rule is concise, easy to understand, and can be easily referenced by team members.

Please create a comprehensive checklist for naming new files to ensure consistency in naming conventions. The checklist should include key elements such as: the required format for file names, guidelines for using dates and version numbers, rules for abbreviations and acronyms, and any specific prefixes or suffixes that should be used. Additionally, include tips on avoiding common pitfalls, such as using special characters or spaces. Format the checklist in a clear and organized manner, making it easy to follow for anyone creating new files.

Please insert a comment at the top of [FILE_NAME] that clearly explains the naming convention used throughout the code. The comment should include details on the rationale behind the chosen conventions, any specific patterns or rules that should be followed, and examples of how to apply these conventions in practice. Ensure the comment is concise yet informative, ideally no more than five sentences, so that it provides a quick reference for future developers working on this file.

Please provide a clear and detailed definition of the naming convention used in the project for inclusion in CLAUDE.md. The definition should cover the rationale behind the naming choices, examples of consistent naming patterns, and any specific rules or guidelines that should be followed. Ensure that the wording is precise and can be easily understood by all team members. Aim for a length of about 150-200 words to fully capture the necessary details.

Please create a guard rule for naming convention adherence that can be included in a markdown file named CLAUDE.md. The rule should specify the naming conventions to be followed, including examples of acceptable and unacceptable names. Additionally, outline the criteria for checking naming consistency, such as case sensitivity, use of underscores or hyphens, and any specific prefixes or suffixes that should be included. Format the rule clearly so that it can be easily understood and implemented by developers.