AI Prompts for Aligning Code with Linting Rules

Please analyze my ESLint configuration provided below: [PASTE CONTENT]. Identify which rules are currently ignored and not being followed in the recent code generation. For each rule, explain why it may have been ignored, and provide suggestions on how to address these issues in the codebase. Additionally, include any potential impact on code quality and maintainability if these rules are not adhered to.

Please review my Prettier configuration provided below: [PASTE CONTENT]. Analyze the generated code and identify any formatting rules that are not being followed according to the Prettier guidelines. For each violation, provide a brief explanation of the rule and suggest how to correct the formatting issues. Additionally, summarize the overall compliance status of the code with respect to the Prettier configuration.

Please review the linting setup for my project based on the following content from my .cursorrules file: [PASTE CONTENT]. Analyze the rules defined in this file and confirm whether they are correctly recognized and understood. Additionally, provide feedback on any potential issues or improvements that could enhance the linting process. Summarize your findings in a clear and structured format, highlighting any rules that may need adjustment or clarification.

Please review the following code snippet: [PASTE CODE]. Analyze it for any violations of ESLint or Prettier rules, and provide a detailed report on each violation found. For each issue, include the specific rule that is being violated, a brief explanation of why it is considered a violation, and suggestions for how to correct it. Additionally, summarize the overall code quality and any improvements that could be made to enhance readability and maintainability.

Please explain your interpretation of the following ESLint rule: [PASTE RULE]. Include details on how this rule should be applied in code generation, providing examples of both correct and incorrect implementations. Additionally, discuss any common pitfalls developers might encounter when adhering to this rule and suggest best practices for ensuring compliance. Your response should be structured clearly and provide insights that would help someone understand the rule's significance in maintaining code quality.

Please modify the code generation logic to strictly adhere to the ESLint rule specified as [PASTE RULE]. Ensure that all generated code complies with this rule by checking for any violations and correcting them accordingly. Provide a detailed explanation of how the adjustments improve code quality and maintainability. Additionally, include examples of code snippets before and after the modifications to illustrate the changes made.

Please review the generated code and ensure it complies with the following Prettier configuration: [PASTE CONFIG]. Identify any areas where the code does not meet these standards and provide specific suggestions for corrections. Additionally, summarize the key differences between the current code format and the Prettier standards, and explain why adhering to these standards is important for code quality and maintainability.

Revise the .cursorrules file to include explicit instructions for adhering to the following linting rules: [PASTE RULES]. Ensure that each rule is clearly defined and provides guidance on how to implement it effectively within the codebase. Additionally, include examples of common mistakes related to each rule and how to avoid them. The final output should be structured in a way that makes it easy for developers to understand and follow these guidelines. Please format the instructions in a clear, numbered list for better readability.

Please review the following list of code violations: [PASTE VIOLATIONS]. For each violation, provide a corrected version that complies with the project's linting standards. Additionally, explain the changes made and why they were necessary to ensure adherence to the standards. Format your response as a clear list, showing the original violation alongside the corrected code.

Enhance my understanding of the following specific linting rules: [PASTE RULES]. Provide a detailed explanation of each rule, including its purpose, common violations associated with it, and best practices for compliance. Additionally, suggest strategies for integrating these rules into my coding workflow to prevent future violations effectively. Aim for a comprehensive overview that I can refer to while coding.

Please perform an ESLint check on the following files: [LIST FILES]. Identify and report any remaining violations, including the type of violation, the specific line number, and a brief description of each issue. Additionally, provide suggestions for how to resolve these violations to ensure code quality and adherence to best practices. Format the report in a clear and organized manner, highlighting the most critical issues first.

Please apply Prettier formatting to the following files: [LIST FILES]. After formatting, confirm that each file complies with the specified configuration settings. Provide a summary of any changes made, including details on which files were successfully formatted and any that did not comply, along with the reasons for non-compliance. Additionally, suggest any necessary adjustments to the configuration to improve compliance in the future.

Please validate the contents of the .cursorrules file to ensure accuracy. Confirm that all linting rules are correctly implemented and functioning as intended. Provide a summary of any discrepancies found, including specific rules that may not be applied correctly. Additionally, suggest any necessary corrections or improvements to enhance the linting process. Format your response in a clear and organized manner.

Please review the following corrected code: [PASTE CODE]. Verify that it adheres to all ESLint and Prettier rules, and provide feedback on any remaining issues or areas for improvement. Additionally, summarize any changes that were made to ensure compliance with these coding standards and suggest best practices for future code submissions. Your response should be clear and structured, highlighting both strengths and weaknesses in the code.

Please conduct a final check on the project to confirm that there are no remaining linting violations. Provide a detailed report that lists any issues found, including the specific files and lines where violations occur, as well as a summary of the types of violations identified. If no violations are present, please confirm that the project is clean and compliant with the established coding standards. Format the report clearly, highlighting any areas that may need attention if violations are found.

Draft a new rule for CLAUDE.md that enforces strict adherence to ESLint rules. This rule should specify the particular ESLint rules that must be followed, including any exceptions or special cases that need to be considered. Additionally, provide a rationale for why this rule is necessary based on recent issues encountered, and outline the potential impact of non-compliance. Format the rule clearly, including examples of compliant and non-compliant code snippets to illustrate the expectations.

Create a comprehensive checklist for ensuring compliance with Prettier formatting standards before finalizing any code generation. The checklist should include specific items such as verifying consistent indentation, ensuring proper line length, checking for trailing commas, and confirming that all code is formatted according to Prettier's rules. Additionally, include steps for running Prettier in different environments and any common pitfalls to avoid. Format the checklist in a clear, organized manner with bullet points for easy reference.

Please create a comprehensive set of guidelines for writing effective code comments that emphasize important linting rules to follow during development. Include sections on the purpose of comments, best practices for inline comments, and guidelines for block comments. Additionally, cover common linting rules that should be adhered to, such as comment formatting, clarity, and relevance to the code. Ensure the guidelines are structured in a clear format, with bullet points or numbered lists for easy reference.

Help me establish a comprehensive set of naming conventions for our codebase that align with our ESLint rules. The conventions should cover variable names, function names, class names, and file names, ensuring clarity and consistency throughout the project. Please provide examples for each category and explain the reasoning behind each convention to help the team understand their importance. Additionally, outline any potential pitfalls to avoid when implementing these conventions to prevent future violations.

Design a project guard script that automatically checks for linting compliance before code is committed. The script should be able to integrate with [VERSION CONTROL SYSTEM] and run the linting process on all staged files. Include options for customizing linting rules based on project requirements, and provide clear feedback to the developer if any files do not comply. Additionally, ensure that the script can be easily configured to run on different branches or specific file types, and document how to set it up in the project README.