AI Prompts for Removing Debug Statements from Code

Please scan the current file for any instances of console.log, debugger, or print statements. Create a comprehensive list of these debug statements, including the line numbers where they appear. For each statement, provide a brief description of its purpose and any relevant context that may help in understanding its role in the code. Format the output in a clear, organized manner, such as a table or bullet points, to facilitate easy review.

Please examine the codebase for common patterns where debug statements are frequently left. Identify specific areas or functions where these statements tend to accumulate and provide examples of the code snippets. Additionally, explain the potential impact of these debug statements on performance and readability, and suggest best practices for managing them effectively. Format your findings in a clear report that includes code examples and recommendations.

Please analyze the last [NUMBER] commits in the repository and identify any debug statements that have been added. For each debug statement found, provide the corresponding file name and line number where it appears. Additionally, summarize the context of each commit to help understand the purpose of the debug statements and whether they align with the overall project goals.

Please review all currently open files in the project and identify any debug statements that are present. For each file, provide a summary that includes the file name, the line numbers where debug statements are located, and a brief description of each debug statement's purpose. Additionally, highlight any redundant or unnecessary debug statements that could be removed to improve code clarity. Format the summary in a clear, organized manner for easy reference.

Please search through the project tree for all instances of debug statements. For each debug statement found, provide the corresponding file path and a brief description of the context in which the debug statement is used. Organize the findings in a clear format, listing each file path alongside the relevant debug statement. Aim to include at least [NUMBER] results in your report.

Please review the current file and identify all instances of console.log statements. Remove these statements and provide a summary of the changes made, including the number of lines removed and any relevant context about the impact of these changes on the code's functionality. Ensure that the final output is clean and does not include any console.log statements, and confirm that the file is functioning correctly without them.

Please find and delete all debugger statements in the currently open files of my project. After you have completed this task, provide a detailed confirmation that includes the specific lines where the debugger statements were removed. Additionally, summarize any potential impacts this may have on the functionality of the code. Ensure that the final output is clear and easy to understand.

Please locate all debug print statements in the project and provide a comprehensive list of the files and specific lines where these statements are found. After identifying them, suggest appropriate modifications to remove or replace these debug prints with more suitable logging methods. Ensure that the final output includes a summary of the changes made and any potential impacts on the project's functionality. Format the response in a clear and organized manner for easy reference.

Refactor the sections of code that currently contain debug statements to make them suitable for production use. Identify specific debug statements that need to be removed or modified, and explain the rationale behind each change. Additionally, ensure that any necessary logging is implemented in a way that maintains performance and security standards. Provide a summary of the refactored code, highlighting the key improvements made and any potential impacts on functionality.

Please help me write a commit message for my code changes after I have removed all debug statements. The commit message should clearly summarize what changes were made, why the debug statements were removed, and any implications this has for the overall functionality of the code. Additionally, include any relevant information about the code that may help others understand the context of these changes. Aim for a concise yet informative message that follows best practices for commit messages.

Please re-scan the current file for any remaining debug console logs. Provide a detailed report on the findings, specifying the locations of any debug statements that were found, and confirm whether all debug statements have been successfully removed. If any debug statements are still present, include recommendations on how to address them. Format the results in a clear list for easy reference.

Please perform a comprehensive review of the entire project to ensure that all debug console logs and statements have been completely removed. Identify any remaining instances of debug logs and provide a summary of their locations. Additionally, check for any potential performance issues that may arise from leftover debug statements and suggest best practices for maintaining project cleanliness moving forward.

Please execute the complete test suite for the project to verify that no debug console logs are interfering with the overall functionality. Provide a detailed report of any issues encountered during the testing process, including the specific test cases that failed and the nature of the interference caused by the debug statements. Additionally, suggest potential solutions or adjustments that could be made to resolve these issues. Ensure the report is structured clearly with sections for each test case and the corresponding results.

Please review the commit history for the project and identify any instances where debug console logs may have been reintroduced. Summarize your findings in a clear and concise manner, highlighting specific commits that added debug statements back into the codebase. Additionally, provide recommendations on how to prevent this from happening in the future, and suggest best practices for maintaining clean code. Format your summary as a brief report that includes the total number of relevant commits and any patterns you observe.

Please draft a message to the team confirming that all debug statements have been successfully removed from the codebase. Include any relevant feedback that was received during the review process, highlighting key points or suggestions made by team members. Ensure the message is clear and concise, and encourage the team to reach out if they have any further questions or concerns regarding this change.

Write a new rule for CLAUDE.md that prevents the inclusion of debug statements in production code. The rule should clearly define what constitutes a debug statement and outline the consequences of including such statements in production. Additionally, provide examples of acceptable and unacceptable code snippets to illustrate the rule effectively. Ensure the rule is concise, easy to understand, and can be easily referenced by team members during code reviews.

Please provide a comment that can be inserted in critical sections of the codebase to remind developers to remove debug statements before finalizing their work. The comment should clearly state the importance of this action and encourage best practices in code maintenance. Format the comment in a way that is easily recognizable and can be understood by all team members. Include a brief explanation of why removing debug statements is essential for code quality and performance.

Please create a comprehensive checklist for developers to follow before committing code. The checklist should ensure that no debug statements are present in the final code. Include specific items such as reviewing all code for console logs, confirming that all debugging tools are disabled, ensuring that unit tests are passing, and verifying that code adheres to the project's style guidelines. Format the checklist in a clear, numbered list for easy reference.

Propose a detailed naming convention for temporary debug variables that will help developers easily identify and remove them from the codebase. The convention should include specific prefixes or suffixes to indicate that a variable is for debugging purposes, guidelines on how to structure the names for clarity, and examples of good and bad naming practices. Additionally, explain the importance of maintaining this convention in terms of code readability and maintainability, and suggest best practices for reviewing and cleaning up debug variables during the development process.

Create a project guard that automatically flags debug statements during code reviews. Describe the mechanism by which this guard identifies and highlights these statements, including any specific rules or patterns it should look for. Additionally, outline the benefits of implementing this guard in terms of code quality and team efficiency. Provide examples of how flagged statements can be addressed and the best practices for maintaining clean code in the project.