AI Prompts for Removing Debug Statements Automatically

Please scan the entire codebase for any instances of console.log, debugger, or debug print statements. For each occurrence, provide the file name and line number where it is found. Additionally, categorize the statements based on their purpose, such as logging variable values, indicating function entry or exit, or tracking errors, and summarize the findings in a clear report format.

Please review the latest commits in the project repository and identify any debug statements that have been added. Summarize your findings in a clear and concise manner, highlighting the purpose of each debug statement and any potential impact they may have on the functionality of the application. Additionally, note if there are any patterns or common issues that emerge from these debug statements. Format your summary in bullet points for easy readability.

Analyze the edits made in Cascade mode and identify any debug statements that may have been unintentionally added or retained. Provide a detailed list of these instances, including the specific locations within the code where these debug statements occur. Additionally, explain the potential impact of these debug statements on the functionality and performance of the application. Ensure that your analysis is thorough and formatted in a clear manner for easy reference.

Please review the following CLAUDE.md file content: [PASTE CONTENT]. I need you to confirm whether the rules regarding debug statements are being adhered to throughout the document. If there are any discrepancies or areas where the rules are not being followed, please highlight those specifically and provide suggestions for how to correct them. Additionally, summarize the overall compliance of the document with regard to the debug statement guidelines.

Evaluate the current codebase for quality issues specifically related to debug statements. Identify any instances of excessive, insufficient, or poorly formatted debug logs that may impact performance or readability. For each issue found, provide a brief explanation of why it is a concern and suggest improvements or best practices for logging. Format the report with clear headings for each identified issue, and include examples from the codebase where applicable. Aim for a comprehensive overview that can guide future development efforts in maintaining high code quality.

Please analyze the provided codebase and identify all instances of console.log, debugger, and debug print statements. Remove each of these statements from the code while ensuring that the overall functionality of the code remains intact. After completing the removal, provide a summary of the changes made, including the number of statements removed and any potential impacts on the code's behavior. Confirm that the code is functioning correctly without these debug statements.

Please identify and correct any errors that have been introduced by Cascade mode related to debug statements in the code. Analyze the specific areas where these errors occur and provide detailed explanations of the changes made to resolve them. Additionally, summarize the fixes in a clear format, highlighting the key modifications and their impact on the overall functionality. Ensure that the summary is concise yet comprehensive enough for someone to understand the adjustments without needing to reference the original code.

Review the provided code and ensure that all debug statements adhere to the guidelines outlined in the CLAUDE.md document. Identify any instances where the code does not comply, and make the necessary adjustments to align with these rules. Additionally, provide a summary of the changes made, explaining how each adjustment improves the clarity and effectiveness of the debug statements. Format your response as a detailed report, including before-and-after code snippets where applicable.

Please refactor the code that currently uses debug statements to implement proper logging mechanisms instead. Ensure that all instances of debug statements are replaced with appropriate logging calls that follow best practices. Provide a summary of the changes made, including the specific logging levels used (e.g., INFO, WARN, ERROR) and any additional context that may help in understanding the logging structure. Additionally, confirm that the new logging implementation is functioning correctly and provide examples of how the logs will appear in the output.

Please review the code provided and identify any unnecessary debug statements that can be removed to enhance overall code quality. For each debug statement you remove, provide a brief explanation of why it was deemed unnecessary and how its removal contributes to cleaner code. Additionally, compile a report summarizing the improvements made, including the total number of debug statements removed and any other enhancements that were implemented to optimize the code. Format the report in a clear and organized manner, highlighting key changes and their impact on the codebase.

Please conduct a thorough scan of the codebase to identify and confirm the removal of all debug console logs. The scan should cover all files and directories within the project. After completing the scan, generate a detailed report that lists any remaining debug statements found, along with their locations in the code. Additionally, provide a summary confirming whether the codebase is now free of debug logs, and include any recommendations for maintaining clean code in the future.

Please review the code and validate its compliance with the CLAUDE.md guidelines specifically related to debug statements. Identify any areas where the code meets the requirements and highlight any sections that may still need adjustments to ensure full compliance. Provide a summary of your findings, including specific examples of compliant and non-compliant debug statements, and suggest any necessary changes for improvement.

Conduct a series of performance tests on the application to verify that the removal of debug console logs has not adversely affected its performance. Measure key metrics such as response time, memory usage, and CPU load before and after the removal. Provide a detailed report of your findings, including any significant changes in performance metrics, and suggest any further optimizations if necessary. Format the results in a clear and concise manner, using graphs or tables where appropriate to illustrate the differences.

Please conduct a thorough check for any errors or issues that may have arisen from the removal of debug statements in the codebase. Provide a detailed report of your findings, including any specific error messages encountered, the locations in the code where these issues occur, and potential impacts on functionality. Additionally, suggest any necessary fixes or adjustments that should be made to resolve these issues. Format the report in a clear and organized manner, using bullet points for easy readability.

Please evaluate the quality of the code after the recent fixes have been applied. Your assessment should include a review of adherence to coding standards, readability, maintainability, and performance considerations. Additionally, identify any potential issues or areas for improvement, and suggest specific changes or enhancements that could elevate the code quality. Format your feedback in a structured manner, highlighting key points and providing examples where applicable.

Draft a new rule for CLAUDE.md that addresses the prevention of debug statements in production code. The rule should clearly outline the reasons for avoiding debug statements in production, including potential performance impacts and security risks. Include specific examples of acceptable logging practices and guidelines for developers to follow when writing production code. Format the rule in a clear and concise manner, suitable for inclusion in the CLAUDE.md documentation.

Create a code comment template that serves as a reminder for developers to remove debug statements before finalizing their code. The template should include sections for the purpose of the debug statement, the date it was added, and a checklist to confirm its removal. Additionally, provide guidelines on best practices for using debug statements in code, including when to use them and how to ensure they do not remain in the production version. Format the template clearly, making it easy for developers to follow and implement.

Please create a comprehensive checklist for developers to use at the beginning of each coding session to ensure that no debug statements are left in the code. The checklist should include specific items such as reviewing recent changes, confirming that all debug logs are removed, checking for commented-out code that may contain debug information, and ensuring that all test cases are updated. Format the checklist in bullet points for clarity and include at least five key items that developers should verify before proceeding with their work.

Propose a detailed naming convention for debug console logs that clearly distinguishes them from production code. The convention should include specific prefixes or suffixes to be used in log statements, such as "[DEBUG]" or "[LOG]", and guidelines on how to format the log messages for clarity. Additionally, explain how this naming convention can facilitate the identification and removal of debug code during the development and deployment process. Provide examples of log statements using the proposed naming convention to illustrate its application.

Please help me design a project guard that automatically flags debug statements during code reviews. Outline the key components of the guard, including how it will be integrated into the existing code review process. Specify the criteria for what constitutes a debug statement and how the guard will notify reviewers of these flags. Additionally, provide recommendations for best practices to ensure that the guard is effective and does not hinder the review process. Include any potential challenges and solutions for implementing this guard in a team environment.