AI Prompts for Ensure Code Style Compliance

Please analyze the last generated output for any ESLint style violations. Quote the specific ESLint rule that was violated and identify the function or component where this violation occurred. Additionally, provide the exact line number of the violation and explain briefly why this rule is important for code quality.

Please analyze the ESLint output provided below: [ESLINT OUTPUT]. Identify and summarize the specific error messages related to style violations. For each violation, explain the nature of the issue and suggest a recommended fix. Format your response as a clear list, detailing the error message, the reason it is a violation, and the proposed solution for each item.

Please explain your interpretation of the last instruction I provided regarding code generation. Specifically, identify the style conventions I expected you to follow, including any formatting rules, naming conventions, or structural guidelines. After your explanation, generate a code snippet that adheres to these conventions, ensuring clarity and consistency in your output.

Compare the expected code style with the actual code generated in the last output. Identify and list specific style rules that were not adhered to, including examples from the code. Additionally, provide suggestions on how to align the actual code with the expected style, ensuring clarity and adherence to best practices. Format the output as a detailed report with sections for each style rule and corresponding examples.

Identify the specific coding style rule that was violated in the last output. Please quote the exact clause from the ESLint configuration that was not adhered to, and provide a brief explanation of how this violation affects code quality. Additionally, suggest a possible correction to align with the specified coding style.

Please review the function signature at src/components/MyComponent.js:15. The original signature is function myComponent(props) { ... } and it has been changed to function MyComponent(props) { ... }. Revert the name change back to 'myComponent' only. Before applying the change, provide me with the diff output that highlights the modification made.

Reformat the code block located at [FILE PATH] on line [LINE NUMBER] to comply with Prettier rules. Ensure that the indentation and spacing are corrected according to the project's Prettier configuration. Provide the reformatted code block as output, highlighting any changes made for clarity.

Please review the import statement for 'react' in the file src/App.js. Change the formatting to ensure consistent spacing, specifically from `import React from 'react';` to `import React from 'react';`. Make sure that no other part of the file is altered during this process. Provide a brief summary of the changes made and confirm that the formatting is now consistent.

Please review the code in the file src/components/Button.js for style consistency. Specifically, identify the naming convention issue where 'Button' does not match the project's style guide. Update the component name to 'button' and provide the revised code snippet reflecting this change.

Please review the file src/services/api.js and identify the missing import statement for 'axios'. Add the line `import axios from 'axios';` at the top of the file, ensuring it is correctly positioned among the other import statements. After making this change, provide a brief summary of the modifications made and confirm that the import is functioning correctly.

Please run ESLint on the project and check for any style violations in the console output. After the check, summarize any remaining issues that are reported, including the specific rules that were violated and suggestions for resolving them. Format the summary in a clear list, detailing the line numbers and descriptions of each issue.

Please provide the code diff for the changes made in [FILE PATH], specifically focusing on the modifications to the function signature. Ensure that the changes are clearly highlighted and that they comply with the established style guide. Format the output to show the original and modified lines side by side for easy comparison.

Replay the last code generation scenario and analyze the generated output for compliance with ESLint rules. Please provide the output along with a detailed confirmation of whether it adheres to the specified ESLint rules. If there are any violations, list them and suggest corrections to ensure compliance.

Please review the code in [FILE PATH] for any edge cases that may have been impacted by the recent changes. Specifically, identify any areas where functionality might be compromised and ensure that the code adheres to the required style guidelines. Provide a summary of your findings, including any necessary adjustments or confirmations of compliance.

Please verify the file state of [FILE PATH] after applying the style conventions. Confirm whether [FILE PATH] now matches the expected style guidelines. Additionally, provide the current content of the file, highlighting any changes made to align with the style conventions.

Before any code generation, please verify ESLint compliance and Prettier formatting for the project. If any violations are found, stop the process and notify the user before continuing. Ensure that no code is generated without confirming style compliance first.

Create a conversation starter template for discussing code style issues. Begin with the statement: 'When generating code, ensure adherence to the following style rules: [LIST SPECIFIC RULES].' Then, instruct the AI to provide a detailed explanation of any rule that is violated before proceeding with the code generation. Ensure the template encourages constructive dialogue and clarity on the importance of each style rule.

Please implement a code comment guard in all generated files to prevent style violations. Use the format '// eslint-disable-next-line [SPECIFIC_RULE]' to disable specific rules on designated lines. Ensure that this comment is included in all code snippets generated, and provide a summary of where these comments are applied within the code.

Create a project convention message that clearly communicates the following guidelines: 'All generated code must adhere to ESLint and Prettier rules. Any deviations must be corrected before deployment. Ensure compliance with the project style guide at all times.' Format this message in a professional tone suitable for a team announcement and include a reminder about the importance of maintaining code quality.

Please create a self-check request for the agent to run before generating code. The request should include a compliance check for ESLint and Prettier rules. If any violations are detected, the agent should stop the process and alert the user with detailed information about the violations found.