AI Prompts for Removing Debug Statements in Code

Please scan the current file for any instances of console.log, debugger, or debug print statements. For each instance you find, provide the exact line number and the corresponding statement. Additionally, summarize the purpose of each statement based on its context in the code. Present the findings in a clear, organized format that includes line numbers and statements for easy reference.

Please analyze the provided code and explain the usage of console.log or debugger statements within it. Discuss their purpose and whether they are essential for the current functionality of the code. Additionally, provide insights on how their presence might affect performance or debugging processes. If applicable, suggest alternatives or improvements for logging practices that could enhance code clarity and maintainability.

Please search through all open files in the project and identify every occurrence of console.log, debugger, or debug print statements. For each occurrence, provide the corresponding file name and the specific line number where it is found. Additionally, summarize the context of each statement, including a brief description of what the surrounding code is intended to do, to help understand the purpose of the debug statements.

For each debug statement identified in the code, analyze and describe its potential impact on both performance and security if it remains in the production environment. Consider how each statement could affect the application's efficiency, including any possible slowdowns or increased resource consumption. Additionally, evaluate the security implications, such as the risk of exposing sensitive information or creating vulnerabilities that could be exploited by malicious actors. Provide a detailed report that outlines these impacts and suggests best practices for managing debug statements in production code.

Please summarize the findings from the debug statement search in my codebase. Include the total number of debug statements found, along with their specific locations in the code (file names and line numbers). Additionally, provide insights on any patterns observed in the placement of these statements and suggest areas where logging could be improved for better debugging in the future.

Please review the current file and remove all instances of console.log, debugger, and debug print statements. After completing the removal, provide a summary of the changes made, including the number of statements removed and any relevant context about the impact of these changes on the code's functionality. Ensure that the final output maintains the integrity of the code and does not introduce any errors.

Please help me replace all console.log statements in my code with a proper logging mechanism that is suitable for production use. Provide a detailed explanation of the benefits of using a logging library over console.log, and suggest a specific logging library that fits well with my project. Additionally, outline the steps I should follow to implement this logging library, including any necessary configuration settings and examples of how to use it effectively in my code. Make sure to highlight best practices for logging in a production environment.

Please review the existing debugger statements in my code and suggest appropriate error handling mechanisms to replace each one. For each statement, provide a brief explanation of why the suggested mechanism is suitable and how it improves the robustness of the code. Additionally, include examples of how to implement the error handling in the context of the surrounding code. Ensure that the suggestions are tailored to the specific errors that might arise in the given codebase.

Refactor the existing code to improve the debug logic by replacing any direct debug statements with conditional logging or appropriate error handling mechanisms. Ensure that the new implementation maintains the same functionality while enhancing performance and readability. Provide clear comments explaining the changes made and the rationale behind using conditional logging or error handling. Additionally, include examples of how the new logging will behave under different conditions, and ensure that all edge cases are accounted for in the refactoring process.

Please review the current file and confirm that all debug statements have been removed or replaced with appropriate alternatives. Provide a summary of any remaining debug statements, including their locations and suggested replacements. Additionally, check for any potential issues related to code cleanliness, such as unused variables or commented-out code, and list them for further action. Ensure that the final output maintains a clean and efficient code structure.

Please scan the current file and identify any remaining debug statements, including console.log, debugger, or debug print statements. Provide a list of these statements along with their line numbers for easy reference. Additionally, suggest appropriate comments or actions to take for each identified statement, such as removing them or replacing them with more suitable logging mechanisms. Ensure that the output is clear and organized for easy implementation.

Please run the existing tests for the codebase to ensure that all functionalities are working correctly without the debug statements included. Provide a summary of the test results, indicating which tests passed and which failed, along with any error messages or issues encountered during the testing process. Additionally, please highlight any areas of the code that may require further attention based on the test outcomes. Format the results in a clear and organized manner for easy review.

Please validate the implementation of the new logging mechanism in the codebase. Check that all relevant functions are logging the appropriate messages at the correct levels (e.g., info, warning, error) and that the logs are being outputted to the designated console or log file. Additionally, ensure that any edge cases are covered and that the logging does not negatively impact the application's performance. Provide a summary of your findings, including any issues discovered and recommendations for improvement.

Please verify that all error handling mechanisms in the code are functioning correctly after replacing debugger statements with appropriate error handling logic. Provide a detailed analysis of how each error is being handled, including any changes made to the code structure. Additionally, outline any potential edge cases that may not be covered by the current error handling and suggest improvements if necessary. Include examples of how the error handling should respond in different scenarios.

Please generate a detailed report that confirms the code is clean of any debug statements and is ready for production. The report should include an overview of the code review process, any identified issues or areas for improvement, and a summary of the steps taken to ensure the code meets production standards. Additionally, provide recommendations for maintaining clean code practices moving forward. Format the report in a clear and professional manner, suitable for sharing with the development team.

Draft a new rule for a CLAUDE.md file that prohibits the use of console.log and debugger statements in production code. The rule should clearly state the rationale behind this prohibition, including potential performance impacts and security concerns. Additionally, provide examples of acceptable alternatives for debugging during development and outline the consequences of violating this rule. Format the rule in a clear, structured manner suitable for inclusion in a coding standards document.

Create a code comment template that serves as a reminder for developers to remove any debug statements before committing their code. The template should include a clear warning about the importance of cleaning up debug logs to maintain code quality and prevent unnecessary clutter in the codebase. Additionally, provide a checklist of items to verify before finalizing a commit, such as ensuring all debug statements are removed, confirming that the code is functioning as intended, and reviewing any potential impacts on performance. Format the template in a way that is easy to copy and paste into code comments.

Please create a detailed checklist for developers to use before starting a coding session. The checklist should include specific items to verify that no debug statements are left in the code, such as reviewing recent code changes, checking for console log statements, ensuring proper error handling is in place, and confirming that all test cases are passing. Additionally, include steps for verifying that the code adheres to the project's coding standards and best practices. Format the checklist in a clear, numbered list for easy reference.

Please propose a detailed naming convention for temporary debug variables in code. The convention should include specific prefixes or suffixes that clearly indicate the variable's purpose as a debug tool, making it easy to identify and remove later. Additionally, provide examples of how this convention can be applied in different programming languages, and suggest best practices for maintaining consistency across a codebase. Aim for a comprehensive guideline that can be easily referenced by developers.

Please create a project guard script that automatically scans for debug statements in code before it is merged into the main branch. The script should identify common debug patterns, such as console.log or print statements, and flag them for review. Additionally, include a notification system that alerts developers when debug statements are detected, providing guidance on how to remove or replace them. Ensure the script is easy to integrate into existing workflows and can be configured to allow exceptions for specific cases. Provide documentation on how to set up and customize the script for different projects.