AI Prompts for Replacing Hardcoded Values with Env Variables

Please scan the project directory for any hardcoded values or secrets that may pose a security risk. Generate a detailed report that includes a list of files where these hardcoded values are found, along with the specific line numbers for each occurrence. Additionally, categorize the types of hardcoded values identified, such as API keys, passwords, or sensitive configuration settings. Ensure the report is clear and structured, making it easy to understand the potential vulnerabilities present in the code.

Please review the codebase for instances where environment variables are defined but not utilized. Provide a detailed list of these variables, including their names and locations within the code. Additionally, explain the potential implications of having unused environment variables in the code, such as security risks or unnecessary complexity. Format the output in a clear table with columns for the variable name, location, and a brief explanation of each instance.

Please analyze the provided configuration files for any hardcoded values. Identify and list all instances where hardcoded values are present, and explain why each should be replaced with environment variables. Additionally, suggest appropriate environment variable names for each identified value, and provide a brief rationale for the replacement. Format your findings in a clear report that includes sections for each file analyzed, the hardcoded values found, and the recommended changes.

Identify and evaluate the security risks associated with hardcoded secrets in the codebase. Consider potential vulnerabilities that may arise from exposing sensitive information, such as API keys, passwords, or tokens. Assess the likelihood and impact of these risks, and provide recommendations for mitigating them, including best practices for managing secrets securely. Format your response as a detailed report, including specific examples of risks and suggested solutions to enhance security.

Please review the following CLAUDE.md file content: [PASTE CONTENT]. Analyze the code for compliance with the rules concerning the use of environment variables. Identify any specific violations or areas of concern, and provide suggestions for how to rectify these issues. Additionally, summarize the key compliance requirements related to environment variables that should be adhered to in this context.

Identify all hardcoded values in the provided code snippet. For each hardcoded value, suggest a corresponding environment variable that can be used as a replacement. Include a brief explanation of why each environment variable is appropriate and how it improves the code's flexibility and security. Format your response as a list, clearly indicating the hardcoded value and its suggested environment variable counterpart.

Please provide a detailed guide on how to update configuration files to use environment variables instead of hardcoded values. Include specific examples of configuration files, highlighting the changes needed for each file. Explain the benefits of using environment variables, such as improved security and flexibility, and provide a step-by-step process for implementing these changes. Additionally, outline any potential pitfalls to watch out for during the update process and how to test the new configuration to ensure it works correctly.

Refactor the following code to enhance security by ensuring that all sensitive information, such as API keys and database credentials, are read from environment variables instead of being hardcoded. Please provide a detailed list of the changes made, including the specific lines of code that were modified and the rationale behind each change. Additionally, ensure that the code maintains its original functionality after the refactoring process. Format the output as a clear before-and-after comparison for better understanding.

Review the codebase for the usage of environment variables and identify any inconsistencies in how they are implemented. Provide a detailed report that highlights specific instances of inconsistency, including the variable names and the contexts in which they are used. Additionally, suggest best practices for standardizing the usage of these environment variables throughout the codebase. Include recommendations for any necessary code changes or refactoring to ensure consistency and maintainability.

Please review the current implementation of environment variables in the project and apply the relevant CLAUDE.md rules to ensure they are used correctly. Identify any areas where the rules are not being followed and suggest specific changes to improve compliance. After making the necessary adjustments, provide a summary of the changes made and confirm that all environment variables are now correctly implemented according to the CLAUDE.md guidelines.

Please confirm that all hardcoded values in the project have been successfully replaced with the corresponding environment variables. Provide a detailed report that includes the following: a list of all the hardcoded values that were identified, the environment variables that replaced them, and any discrepancies or issues encountered during the replacement process. Additionally, include a summary of the overall success of the replacement and any recommendations for further improvements or checks that should be made to ensure consistency across the project.

Please run the application and verify that it functions correctly with the updated environment variable configurations. Provide a detailed report on any issues encountered during the testing process, including specific error messages, unexpected behaviors, and any areas where the application performs as expected. Additionally, include a summary of the overall functionality and any recommendations for further improvements or adjustments needed based on your findings.

Please scan the application logs for any errors related to environment variable usage. Provide a detailed report of any issues you find, including the specific error messages, timestamps, and the components of the application affected. Additionally, summarize the potential impact of these errors on the application's functionality and suggest possible solutions or next steps to resolve them.

Please assess the security posture of the application after the recent changes have been implemented. I need a detailed report that confirms whether any secrets or sensitive information are exposed in the codebase or configuration files. Include an analysis of potential vulnerabilities that may have been introduced and provide recommendations for further improvements. Additionally, summarize the overall security enhancements made and their effectiveness in mitigating risks. Present this information in a structured format with clear headings and bullet points for easy reference.

Please conduct a thorough review of the codebase to ensure consistent usage of environment variables. Identify any discrepancies or inconsistencies in naming conventions, formatting, and usage across different files and functions. Provide a detailed report highlighting specific areas where changes are needed, along with suggestions for standardization. Additionally, summarize the overall impact of these inconsistencies on the functionality and maintainability of the code.

Create a new rule for CLAUDE.md that enforces the use of environment variables in project configurations. The rule should specify the required format for defining environment variables, including naming conventions and examples of acceptable values. Additionally, outline the consequences for non-compliance and provide guidance on how to properly implement environment variables in code. Ensure the rule is clear, concise, and easy for team members to follow.

Create a code comment template that encourages developers to use environment variables instead of hardcoding values. The template should include sections for the purpose of the variable, the expected format, and a reminder to check if the variable is set in the environment. Additionally, provide an example of how to retrieve the variable in code and a note on the importance of maintaining security and flexibility by using environment variables. Format the template in a way that can be easily copied and adapted for different programming languages.

Create a comprehensive naming convention for environment variables that promotes clarity and consistency across projects. The convention should include guidelines on naming structure, such as using uppercase letters with underscores to separate words, and should specify how to handle prefixes or suffixes for different types of variables (e.g., production, development). Additionally, provide examples of well-named environment variables that adhere to this convention and explain the reasoning behind each choice. Aim for a format that can be easily referenced by team members to maintain uniformity in future projects.

Please create a comprehensive session-opener checklist for developers to use at the beginning of their coding sessions. The checklist should include specific items to review that will help prevent hardcoding values in their code. Cover aspects such as verifying the use of environment variables, ensuring configuration files are properly set up, checking for the use of constants instead of hardcoded values, and confirming that all sensitive information is stored securely. Format the checklist as a bulleted list with clear, actionable items that can be easily followed.

Please help me establish a project guard that automatically checks for hardcoded values during code reviews. The guard should analyze the codebase for any instances of hardcoded values and flag them for review. Include guidelines on how to implement this guard effectively, what specific values to look for, and how to ensure that the team follows best practices in avoiding hardcoding. Additionally, provide a summary of potential impacts on code quality and maintainability when hardcoded values are present.