AI Prompts for Remove Debug Statements from Production Code

Provide the exact console output from the last deployment that includes debug statements. Identify the specific function or component in the code where these debug statements are located, and summarize the context in which they were used. Include any relevant information that could assist in diagnosing the issue, and format your response clearly by highlighting the output alongside the associated function or component.

Paste the content of your main component file, focusing on the section where you suspect debug statements may exist. Analyze this section for any instances of console.log or debugger statements, and identify which of these statements are unnecessary and should be removed to improve code clarity. For each identified statement, explain why it is not needed and suggest specific improvements to enhance the overall quality of the code.

Explain your interpretation of the instruction to clean up the code. What specific changes are required before fixing the debug statements? Provide a detailed analysis that includes the areas of the code needing attention, potential issues arising from the current state, and best practices to follow during the cleanup process. Additionally, outline the steps you would take to implement these changes effectively, ensuring clarity and maintainability in the code.

Compare the expected behavior of my application during the last deployment, where no debug statements should be present in the production environment, with the actual behavior, which includes console.log or debugger statements. Identify and list the specific instances of these debug statements, including their locations in the code, and analyze the potential impacts they may have on performance or security. Finally, provide a detailed plan with actionable steps to remove these debug statements and implement measures to prevent their reappearance in future deployments.

Identify the specific coding standard or rule that is violated by leaving debug statements in the code. Provide a detailed explanation of why this practice is considered a violation, including potential consequences for production-ready code. Additionally, quote the exact clause from the relevant coding standard documentation that outlines the requirement for clean, production-ready code, and explain how adhering to this standard can improve code quality and maintainability.

Locate all instances of console.log and debugger statements in the file [FILE] at line [LINE]. Remove these statements and provide a detailed diff of the changes made, highlighting what was removed and any relevant context around the changes. Additionally, summarize the impact of these removals on the overall code functionality and performance, and format your response clearly, indicating the original lines and the modified version for easy comparison.

Rewrite the function located at [FILE]:[LINE] to include a guard clause that prevents console.log and debugger statements from executing in a production environment. Ensure the guard clause checks the current environment and allows these statements to run only if it is not in production. Provide the complete implementation of the revised function, making sure that the original logic is preserved while effectively incorporating this safeguard.

Update the function at [FILE]:[LINE] by scoping the debug statements within a conditional that checks if the environment is set to 'development'. Ensure that the debug logs are executed only when this condition is true, and provide the revised code snippet with clear comments explaining the changes made and the purpose of the conditional check.

Provide a detailed guide on enforcing a formatting rule that disallows any console.log or debugger statements in production code for a project. Outline the specific steps required to implement this rule, including necessary configuration changes, tools or libraries that can assist, and methods to test that the rule is being enforced correctly. Additionally, explain how to handle existing code that may violate this rule and suggest best practices for maintaining clean production code moving forward.

Review the imports in [FILE] and identify any debugging tools that may lead to unnecessary console.log statements. Remove any imports that are not essential for the functionality of the code, and provide a brief explanation for each import deemed unnecessary. If applicable, suggest alternatives to the removed imports. Format your response as a summary report detailing the changes made and the rationale behind each decision.

Run the deployment process again and check the console output for any occurrences of console.log or debugger statements. Confirm that these statements do not appear in the output, and provide the full console output for verification purposes. Ensure to highlight any unexpected findings or issues encountered during the process.

Provide the code diff for the main component file after removing debug statements. Clearly highlight the specific changes made, including lines that were deleted and any modifications to existing lines. Additionally, explain why these changes were necessary and how they improve the code's readability or performance. Format the output to distinguish between added and removed lines for easy understanding.

Replay the last scenario that resulted in debug statements. Confirm whether it runs without any debug output and provide a detailed report of the results. Include any differences in behavior compared to the previous run, and specify if any changes were made to the code or environment that could have affected the outcome. Additionally, summarize any insights gained from this replay that could help improve future debugging efforts.

Identify an edge case that previously triggered debug statements in the code. Create a specific test case that replicates this scenario to ensure it functions as expected. Run the test case and confirm that it does not produce any console.log or debugger statements. Finally, provide a detailed summary of the test results, including any observations or changes made to the code that may have affected the output.

Check the final output state of the application after the last deployment. Ensure that there are no debug statements present in the output. Provide a summary of your findings, including any debug statements that were found, and confirm whether the output is clean and ready for production use.

Verify that there are no console.log or debugger statements present in the code before proceeding with deployment. If any such statements are found, halt the deployment process and notify the developer immediately. Additionally, provide a summary of the findings, including the specific locations of any debug statements detected, to ensure the code is clean and ready for production.

Create a checklist for developers to ensure that all debug statements are removed from the codebase before deployment. Include items such as a reminder to search for `CONSOLE.LOG` and `DEBUGGER` statements, a prompt to review recent code changes for any overlooked debug statements, and a confirmation step to ensure that all team members have completed this check. Format the checklist in a clear and concise manner, suitable for inclusion in a deployment checklist document, and provide space for team members to initial their completion of each item.

Implement a code comment guard in the main component file to remind developers to remove any debug statements before committing changes. Place the comment at the top of the file, formatted as follows: '// TODO: Remove any console.log or debugger statements before production deployment.' Additionally, include a brief explanation below the comment that highlights the importance of removing debug statements for production, focusing on their potential negative impact on performance and security.

Draft a project convention message that outlines the policy against leaving debug statements in production code. The message should include the following: 'All developers must ensure that no console.log or debugger statements are present in the code before merging any pull requests.' Additionally, explain the reasons for this policy, including maintaining code quality, preventing performance issues, and ensuring a clean production environment. Ensure the message is formatted in a professional tone suitable for team communication and includes a reminder for developers to thoroughly review their code before submission.

Create a self-check request for an agent to execute before deployment. The request must include a comprehensive scan of the entire codebase for any instances of console.log or debugger statements. If any such statements are detected, the agent should immediately alert the developer and halt the deployment process. The alert should provide specific details about the locations of the statements and emphasize the importance of removing them prior to proceeding with deployment.