20 of the best prompts for resolving inconsistent naming conventions, step by step across 4 stages. Works with ChatGPT, Claude, and Gemini.
20 of the best prompts for resolving inconsistent naming conventions, step by step across 4 stages. Works with ChatGPT, Claude, and Gemini.
Published June 28, 2026
Getting Resolving Inconsistent Naming Conventions right takes more than a single prompt. This 4-stage guide covers Diagnose the Wall, Isolate and Fix, Verify the Resolution, and more, breaking the whole process into focused steps where each prompt builds on the last. Mixing camelCase, snake_case, and PascalCase in the same file causes confusion and reduces code readability. This inconsistency can lead to errors and make maintenance difficult. These prompts help developers enforce a consistent naming convention using GitHub Copilot. Every prompt is optimized and runs in ChatGPT, Claude, and Gemini.
Identify the current naming conventions used in the code file.
Identify Naming Styles
Analyze the following code snippet: [PASTE CODE]. Identify and list the naming conventions used within the code, including variable names, function names, class names, and any other identifiers. For each naming style, provide a brief explanation of its purpose and whether it adheres to common best practices in coding standards. Additionally, suggest any improvements or alternatives that could enhance consistency and readability in the code.
Check for Mixed Conventions
Please review the following code: [PASTE CODE]. Analyze the naming conventions used throughout the code and identify any inconsistencies or mixed conventions. Provide a detailed explanation of the specific areas where naming conventions differ, and suggest a unified naming convention that could be applied to improve code readability and maintainability. Additionally, include examples of how the suggested convention would look in practice within the code.
Detect Naming Inconsistencies
Please examine the following code: [PASTE CODE] and identify any naming inconsistencies present. Provide a detailed analysis that includes the specific variables, functions, or classes that do not adhere to consistent naming conventions. Suggest improvements for each inconsistency you find, explaining why the proposed names would enhance clarity and maintainability. Format your response in a clear list, categorizing the issues by type (e.g., variables, functions, classes) and include examples of both the current and suggested naming.
List Variable Naming Styles
Identify and analyze the variable naming styles used in the following code: [PASTE CODE]. Provide a detailed list of each naming convention, including examples from the code, and explain the context in which each style is typically used. Additionally, discuss any inconsistencies you find and suggest best practices for maintaining uniformity in naming conventions throughout the codebase. Format your response as a structured report with clear headings for each naming style.
Analyze Function Names
Analyze the function names in the following code snippet: [PASTE CODE]. Identify the naming conventions utilized, including whether they follow camelCase, snake_case, or any other style. Provide a summary of any inconsistencies you find, and suggest improvements to ensure uniformity in naming conventions throughout the code. Additionally, explain the importance of consistent naming conventions for code readability and maintainability.
Focus on changing the inconsistent naming conventions to a single, unified style.
Convert to camelCase
Refactor the following code snippet to ensure that all variable and function names are converted to camelCase. Please provide the updated code with clear and consistent naming conventions applied throughout. Ensure that the functionality of the code remains unchanged after the refactoring. Additionally, include comments explaining any significant changes made during the process. Here is the code to refactor: [PASTE CODE].
Switch to snake_case
Please modify the following code to use snake_case for all identifiers. Ensure that all variable names, function names, and any other identifiers are converted appropriately. The code to be modified is: [PASTE CODE]. After making the changes, provide a brief summary of the modifications you made and any potential impacts on the code's readability or functionality.
Adopt PascalCase
Please change the naming convention in the following code to use PascalCase for class names and camelCase for function names. The code to modify is: [PASTE CODE]. Ensure that all instances of class names are updated to PascalCase, while function names are adjusted to camelCase. Provide the modified code with clear annotations indicating the changes made for better understanding.
Unify Naming Convention
Please review the following code: [PASTE CODE] and standardize the naming convention to [SPECIFY CONVENTION]. Ensure that all variable names, function names, and class names are consistent with the specified convention throughout the entire codebase. Provide a clear explanation of the changes made and highlight any areas where the naming convention was particularly inconsistent. Format the output to show the original code alongside the revised code for easy comparison.
Apply Project Naming Rules
Please review the following code: [PASTE CODE] and identify any inconsistencies with the project's naming conventions. Provide a detailed analysis of the naming rules that should be applied, and suggest specific changes to ensure compliance. Additionally, explain the rationale behind each suggested change to enhance clarity and maintainability in the codebase. Format your response in a clear and organized manner, highlighting the original names and the proposed corrections.
Ensure the naming conventions are now consistent throughout the code.
Confirm Naming Consistency
Please review the following code for naming consistency: [PASTE CODE]. Identify any inconsistencies in variable names, function names, and class names according to common naming conventions such as camelCase, snake_case, or PascalCase. Provide a detailed report highlighting any discrepancies, along with suggestions for correcting them to ensure uniformity throughout the codebase. Additionally, summarize the overall adherence to naming conventions in the code.
Validate Naming Changes
Please review the following code: [PASTE CODE] and validate that the naming changes have been applied consistently throughout. Identify any instances where the naming conventions are not followed and provide suggestions for improvement. Additionally, summarize the overall adherence to the naming conventions and highlight any areas that may cause confusion or inconsistency. Your response should be detailed and structured, focusing on clarity and best practices in naming.
Review for Mixed Styles
Please review the following code snippet for consistency in naming conventions. Ensure that there are no mixed styles present, such as camelCase, snake_case, or PascalCase being used interchangeably. Provide feedback on any inconsistencies you find and suggest a unified naming convention that should be applied throughout the code. The code to review is: [PASTE CODE].
Ensure Compliance with Rules
Please review the following code for compliance with the specified naming conventions: [PASTE CODE]. Identify any inconsistencies or violations of the naming rules and provide detailed feedback on how to correct them. Additionally, suggest improvements to enhance code readability and maintainability while adhering to the established naming standards. Format your response in a clear manner, outlining each issue and the corresponding recommendation for resolution.
Check for Naming Errors
Please analyze the following code for any remaining naming errors: [PASTE CODE]. Identify inconsistencies in naming conventions, such as variable names, function names, and class names. Provide a detailed report highlighting each error, explaining why it is considered an inconsistency, and suggest appropriate corrections to align with best practices. Additionally, summarize the overall impact of these naming errors on code readability and maintainability.
Create guidelines and tools to maintain consistent naming conventions.
Draft Naming Convention Rule
Create a detailed rule for a document named CLAUDE.md that enforces the [SPECIFY CONVENTION] naming convention for our project. The rule should outline the specific guidelines for naming variables, functions, and classes, including examples of correct and incorrect usage. Additionally, explain the reasoning behind the convention and how it improves code readability and maintainability. Ensure the rule is clear and concise, making it easy for team members to understand and apply consistently.
Create Code Comment
Please add a detailed comment to the following code snippet: [PASTE CODE]. The comment should explain the naming convention used throughout the code, including any specific rules or patterns that are followed, such as camelCase, snake_case, or PascalCase. Additionally, clarify the rationale behind choosing this naming convention and how it contributes to code readability and maintainability. Aim for a thorough explanation that would help someone unfamiliar with the code understand the naming choices made.
Develop Naming Checklist
Help me develop a comprehensive checklist for developers to ensure consistent naming conventions in their code. The checklist should cover key areas such as variable names, function names, class names, and file names. Include guidelines on naming styles (e.g., camelCase, snake_case), length recommendations, and the importance of clarity and descriptiveness in names. Additionally, provide examples of good and bad naming practices. Format the checklist in a clear, easy-to-follow structure that can be referenced during development.
Formulate Naming Guidelines
Please create a comprehensive set of naming guidelines for our project to ensure consistency in naming conventions across all components. The guidelines should cover various aspects such as variable names, function names, class names, and file names. Include specific examples for each category to illustrate the preferred naming styles and formats. Additionally, outline any rules regarding the use of abbreviations, capitalization, and special characters. Format the guidelines in a clear and organized manner, suitable for inclusion in our project documentation.
Generate Naming Convention Document
Create a comprehensive naming convention document for the project. The document should include guidelines for naming variables, functions, classes, and files, ensuring consistency and clarity throughout the codebase. Specify the preferred naming styles (e.g., camelCase, snake_case) and provide examples for each category. Additionally, outline any exceptions to the rules and the rationale behind the chosen conventions. Format the document in a clear and organized manner, suitable for future reference by all team members.
GitHub Copilot analyzes the open files and uses patterns from the code to suggest naming conventions. It relies on the context provided by the developer.
Copilot may mix conventions if the code it analyzes contains multiple styles. Providing clear examples and rules can help guide its suggestions.
While Copilot suggests code, it cannot enforce conventions. Developers can guide it by providing clear examples and rules in the codebase.
You can influence Copilot's suggestions by consistently using a specific naming convention across your codebase and documenting it in your guidelines.
Review the suggestions and correct them manually. Providing feedback through the tool can help improve future suggestions.
AI Prompts for Standardize Naming Conventions Across Files
Inconsistent naming conventions can lead to confusion and errors in your codebase, making it difficult to maintain and extend your application.
See promptsAI Prompts for Standardize Naming Conventions in Code
Inconsistent naming conventions can lead to confusion and bugs in your code, making it difficult to maintain.
See promptsAI Prompts for Enforcing Consistent Naming Conventions
Inconsistent naming conventions in your codebase can lead to confusion and maintenance headaches.
See prompts