AI Prompts for Removing Debug Statements from Code

Please scan the entire codebase for any instances of debug statements, including console.log, debugger, or print statements. For each occurrence, provide the file name and the corresponding line number where it appears. Additionally, categorize the findings by file type and summarize the total number of debug statements found in the codebase. Present the results in a clear format that allows for easy identification of where these statements are located.

Please analyze the latest commits in the code repository for any added debug statements. Summarize your findings by detailing the specific changes made, including the locations of the debug statements and their purposes. Additionally, evaluate whether these debug statements enhance the clarity of the code or if they could potentially clutter the output. Present your summary in a structured format that includes sections for each commit analyzed, along with recommendations for any necessary adjustments.

Examine the provided codebase and identify common patterns or functions that are utilized for debugging purposes. For each pattern you find, provide a detailed description that includes its purpose, how it is implemented, and any specific examples from the code. Additionally, analyze the effectiveness of these debugging methods and suggest any improvements or alternatives that could enhance the debugging process. Format your response in a structured manner, with clear headings for each identified pattern.

Please analyze the following CLAUDE.md file content: [PASTE CONTENT]. Check if the code complies with the established rules for debug statements. Specifically, identify any instances where debug statements are missing, improperly formatted, or do not follow the guidelines outlined in the document. Provide a summary of your findings, including specific examples and recommendations for improvement.

Identify all custom debugging functions present in the codebase. For each function, provide the following details: the function name, its purpose, how it is used within the code, and the specific locations or files where it can be found. Additionally, include any relevant examples of how these functions are invoked in the code, and discuss any potential improvements or best practices that could enhance their effectiveness. Format the response in a clear and organized manner, using bullet points for each function.

Please analyze the provided codebase and remove all instances of console.log statements. After completing the removal, provide a summary that includes the total number of console.log statements that were found and removed. Additionally, ensure that the functionality of the code remains intact and that there are no unintended side effects from this change. If possible, provide a brief explanation of how the code behaves without these console logs.

Please analyze the provided code and identify all instances of debugger statements. Remove each instance and ensure the code functions correctly without them. After completing the task, provide a summary that includes the total count of removed debugger statements and any other relevant changes made to maintain the code's functionality.

Please review the provided code and remove all print statements that were used for debugging purposes. After completing the removal, provide a summary of the changes made, including the number of print statements deleted and any relevant context about their locations in the code. Ensure that the functionality of the code remains intact and that no other changes are made. Format the summary in a clear and concise manner.

Refactor the custom debugging functions in the codebase. Identify any functions that are no longer necessary and either remove them or improve their implementation for better performance. Provide a summary of the changes made, including the reasons for any removals or modifications, and highlight how these changes enhance the overall functionality and maintainability of the code. Ensure that the refactored code is clean, well-documented, and follows best practices for debugging.

Please review the current codebase and identify any areas where debug statements do not comply with the guidelines outlined in CLAUDE.md. Provide a detailed report highlighting specific instances of non-compliance, including the location in the code and suggestions for how to modify these statements to meet the standards. Additionally, summarize the overall compliance status of the codebase and recommend any best practices for maintaining adherence to CLAUDE.md in future code updates.

Please re-scan the codebase to confirm that all instances of console.log, debugger, and print statements have been removed. Generate a detailed confirmation report that includes the total number of statements found, the locations of any remaining statements, and a summary of the changes made during the removal process. Additionally, indicate if any issues were encountered during the scanning process and how they were resolved. Format the report clearly, with sections for findings, actions taken, and any recommendations for future code reviews.

Please analyze the following code for any remaining debug statements and provide a detailed output of the linter results. The code to review is: [INSERT CODE HERE]. Highlight any lines that contain debug statements, and categorize the issues found based on severity (e.g., errors, warnings, info). Additionally, suggest possible improvements or best practices for cleaning up the code and ensuring it adheres to standard coding conventions.

Please run the following code: [INSERT CODE HERE] and ensure it executes without any interruptions related to debug console logs. If you encounter any issues during execution, provide a detailed report of the errors, including the specific line numbers where the issues occurred and any relevant error messages. Additionally, suggest potential fixes or improvements to address the identified problems.

Please review the provided code and verify its adherence to the CLAUDE.md guidelines specifically related to the inclusion of debug statements. Identify any areas where the code either meets or fails to meet these standards. Provide a detailed assessment that includes examples of compliant and non-compliant debug statements, and suggest improvements where necessary to ensure full compliance with the CLAUDE.md rules.

Please create a detailed report analyzing the current codebase for the presence of debug statements. The report should include sections on the overall structure of the code, specific areas where debug statements are missing, and the potential impact of this absence on debugging and maintenance. Additionally, provide recommendations for best practices regarding the use of debug statements in future code development. Format the report in a clear, organized manner with headings and bullet points for easy readability.

Please draft a new rule for the CLAUDE.md documentation aimed at preventing the inclusion of debug statements in production code. The rule should clearly outline the rationale behind avoiding debug statements, the potential risks associated with their presence in production, and provide examples of acceptable practices for logging in production environments. Additionally, include guidelines on how to properly review code to ensure compliance with this rule. Format the rule in a clear and concise manner suitable for inclusion in the CLAUDE.md file.

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 sections for the purpose of the debug statement, the date it was added, and a checklist to confirm that the debug statement has been removed. Additionally, provide an example of how to fill out the template for a sample debug statement. The final output should be formatted clearly and be easy to understand for all team members.

Create a pre-commit hook script that automatically detects and prevents any debug statements from being committed to the repository. The script should scan all staged files for common debug patterns such as console.log, print, or any other debugging functions specific to the programming language being used. If any debug statements are found, the script should prevent the commit and display a clear error message indicating the presence of these statements. Additionally, provide an example of how to set up this hook in a Git environment, including any necessary configuration steps.

Propose a comprehensive naming convention for temporary debug variables that will facilitate easy identification and removal before production deployment. The convention should include specific prefixes or suffixes that clearly indicate a variable is meant for debugging purposes, along with guidelines on how to structure these names for consistency and clarity. Additionally, explain the rationale behind the chosen convention and provide examples of how it can be applied in different coding scenarios. Aim for a format that is easy to reference and implement across various projects.

Please create a comprehensive checklist for developers to use before starting a coding session. The checklist should ensure that all debug statements have been removed from the code and include additional items such as verifying code functionality, checking for proper documentation, ensuring adherence to coding standards, and confirming that all necessary tests are in place. Format the checklist in a clear, bullet-point style, and aim for at least 10 items to cover all essential aspects of preparation. This will help maintain code quality and prevent issues during the development process.