AI Prompts for Removing Debug Statements from Code

Please scan the generated code for any instances of console.log, debugger, or debug print statements. Create a detailed list that includes each occurrence along with its corresponding line number. Additionally, provide a brief explanation of the context in which each statement is used and suggest whether it should be retained or removed based on best practices for clean code. Format the output in a clear and organized manner for easy reference.

Please analyze the current build of my application and identify all components that are generating console.log or debugger statements. For each component, provide a brief description of its purpose and functionality within the application. Additionally, include the specific locations in the code where these statements are found, and suggest any potential improvements or best practices for logging that could enhance performance and maintainability. Format the findings in a clear, organized list for easy reference.

Please review the recent code changes in the project and identify any modifications that may have introduced debug statements. For each change, provide the specific lines of code where these statements were added, as well as the components or modules that are affected. Additionally, summarize the potential impact of these debug statements on the overall functionality of the application. Format your findings in a clear, organized manner, highlighting any critical areas that may require further attention.

Trace back the origin of each debug statement found in the code for the project. For each statement, provide details on whether it is part of the initial codebase or if it was introduced during later iterations. Additionally, include the specific lines of code where each debug statement appears, along with a brief explanation of its purpose and any relevant context that may help in understanding its role in the overall functionality of the application. Format the output as a structured list for clarity.

Evaluate the impact of the debug statements on the performance of the application. Analyze how these statements may affect response times, resource utilization, and overall user experience. Additionally, identify any potential security issues that could arise from exposing sensitive information through these debug statements. Provide a detailed summary of your findings, including recommendations for optimizing or mitigating any identified risks.

Please review the codebase 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 sections of code affected. Ensure that the code remains functional and does not introduce any errors. Format the summary in a clear, concise manner, highlighting any important considerations for future debugging.

Please lock the components where debug statements were removed to prevent their reintroduction. Provide a list of the components that have been successfully locked, along with a brief explanation of how locking them will help maintain the integrity of the code. Additionally, confirm that the locking process has been completed and outline any next steps that may be necessary to ensure ongoing stability in the project.

Please help me refactor the debugging code in my project by creating a separate logging module that can be easily toggled on or off. The module should include functions for logging different levels of messages, such as info, warning, and error, and should allow for customizable log formats. Additionally, provide guidance on how to integrate this module into the existing codebase, including examples of how to call the logging functions in various scenarios. Ensure that the solution is clean, maintainable, and follows best practices for logging in software development.

Help me establish a code standard that disallows the use of debug statements in production code. The standard should clearly outline the reasons for avoiding debug statements, the potential risks associated with leaving them in production, and the expected practices for developers to follow. Include examples of acceptable logging practices and guidelines for ensuring that debug statements are removed before deployment. Format this as a formal document that can be shared with the development team.

Please rebuild the application while ensuring that no debug statements are included in the code. After the rebuild, confirm the build status and provide a summary of the code cleanliness, including any areas that may need further optimization or review. Additionally, outline any potential issues that could arise from the absence of debug statements and suggest alternative methods for debugging in the future. Format your response in a clear and structured manner.

Please perform a thorough code cleanliness check on the provided codebase. Ensure that there are no debug statements or unnecessary console logs present. After the review, generate a confirmation report detailing any issues found, including the specific lines of code where debug statements were identified. Additionally, provide recommendations for improving overall code cleanliness and best practices for future development.

Please conduct performance tests to evaluate the impact of removing debug statements on application performance. Focus on key metrics such as response time, resource usage, and throughput. Provide a detailed report of the test results, including any improvements observed compared to previous performance benchmarks. Additionally, include any recommendations for further optimization based on the findings.

Please verify the application for security compliance after the removal of debug statements. Assess whether all security protocols are being followed and identify any potential vulnerabilities that may have been introduced during this process. Provide a detailed compliance confirmation report that includes any findings, recommendations for improvements, and an overall assessment of the application's security status. Ensure that the report is structured clearly, with sections for findings, recommendations, and a conclusion.

Please validate that all components of the application function correctly after the removal of debug console logs. Conduct thorough testing on each component, checking for any errors or unexpected behavior. Summarize your findings in a validation report that includes: a list of components tested, any issues encountered, and confirmation of successful functionality for each component. Ensure the report is clear and concise, suitable for sharing with the development team.

Please review the build logs for the project and identify any errors or warnings specifically related to debug statements. Summarize your findings in a clear report, detailing the nature of any issues found, the specific lines or sections of the logs where they occur, and any recommendations for resolving these issues. Additionally, provide an overall assessment of the build logs, indicating whether they meet the required standards for a successful build. Format your response as a structured document with headings for each section.

Create a new rule for CLAUDE.md that addresses the prevention of debug statements in future builds. The rule should clearly outline the rationale for avoiding debug statements, specify the consequences of including them in the code, and provide guidelines for developers on how to handle logging during development and production. Additionally, include examples of acceptable logging practices and any exceptions that may apply. Format the rule in a way that can be easily integrated into the existing CLAUDE.md documentation.

Draft comprehensive guidelines for writing code comments that discourage the use of debug statements. The guidelines should cover the importance of meaningful comments, the difference between debug statements and informative comments, and best practices for commenting code effectively. Include examples of good and bad comments, and specify when to use comments versus relying on clear code structure. Format the guidelines as a structured document with headings and bullet points for clarity.

Please create a comprehensive checklist for session openers that ensures no debug statements are included during the development process. The checklist should cover key areas such as code review practices, testing protocols, and team communication strategies. Include specific items that developers should verify before finalizing their code, such as confirming that debug logs are removed and that the code is clean and production-ready. Format the checklist in bullet points for easy reference and ensure it is thorough enough to prevent any recurrence of this issue.

Define clear naming conventions for logging functions that distinguish them from standard debug statements. Specify the format to be used for naming these functions, including any prefixes or suffixes that should be applied. Additionally, explain the rationale behind these conventions and provide examples of both logging function names and debug statement names to illustrate the differences. Aim for a comprehensive guide that can be easily referenced by the development team.

Help me implement a project guard that automatically flags debug statements during code reviews. Outline the steps needed to set up this guard, including the programming language and framework being used, any specific configurations required, and how to integrate it into the existing code review process. Additionally, explain how to ensure that the guard effectively identifies and highlights debug statements, and suggest best practices for maintaining the guard over time. Provide example code snippets where applicable.