AI Prompts for Preventing Config File Modifications

Please provide a detailed list of all configuration files that have been modified recently in the project. For each file, include the specific changes made, the reasons behind those changes, and how they impact the overall functionality or performance of the system. Additionally, indicate the date of each modification and any related issues or improvements that prompted these updates. Format your response in a clear and organized manner, using bullet points for each file to enhance readability.

Please review the following CLAUDE.md file content: [PASTE CONTENT]. Analyze the rules outlined within the document and confirm your understanding of each rule. After your review, identify which specific rule should have been applied to the last task and explain how it relates to the task at hand. Provide a summary of any discrepancies between the rules and the actions taken in the last task.

Please analyze the recent changes made to the Dockerfile or CI configuration files. Summarize the specific alterations, detailing what was changed, the rationale behind each modification, and how these changes may impact the overall functionality and performance of the application. Additionally, identify any potential issues that could arise from these changes and suggest best practices for future modifications. Format your response as a structured report with clear headings for each section.

Please provide a detailed history of the shell commands executed in the last [NUMBER] days. Analyze the commands to identify any that may have resulted in changes to configuration files, including the specific files affected and the nature of the changes made. Present the findings in a structured format, highlighting the most significant commands and their potential impact on the system's configuration. Include any relevant timestamps and user information associated with each command.

Please review the intended outcome of the last task related to modifying the configuration files. Describe in detail what the specific goals were and how the changes made to the configuration files helped in achieving those goals. Include any relevant metrics or indicators that demonstrate the success of these modifications and suggest any further improvements that could enhance the outcome. Provide a structured summary that highlights the key points clearly.

Please help me revert the modifications made to the Dockerfile or CI configuration files. I need the files to match the previous stable version exactly. Provide a detailed comparison of the changes that were made, and outline the steps necessary to restore the files to their original state. Additionally, include any potential issues that might arise during the reversion process and how to address them.

Please provide a detailed plan for implementing a mechanism to lock the Dockerfile and CI configuration files to prevent unintended modifications. Outline the specific steps that will be taken, including any tools or methods that will be used to enforce this locking mechanism. Additionally, explain how you will ensure that only authorized personnel can make changes and how you will handle any necessary updates or modifications in the future. Include considerations for testing the effectiveness of this locking mechanism and any potential challenges that may arise during implementation.

Please review the instructions outlined in the CLAUDE.md file regarding the current task. Clarify the key steps that need to be followed to ensure that configuration files remain unaltered throughout the process. Provide a detailed breakdown of any specific actions that should be taken, as well as any precautions that need to be observed to prevent unintended changes. Summarize the clarified instructions in a clear and concise format that can be easily referenced during the task execution.

Please adjust the file permissions for the configuration files located in [DIRECTORY PATH]. Ensure that the permissions are set to [SPECIFIC PERMISSIONS] to prevent unauthorized edits. After making the changes, confirm the new permissions by providing a summary of the updated settings and any relevant details about the changes made. Additionally, explain how these new permissions enhance security and prevent unauthorized access.

Please re-execute the task using the corrected parameters while ensuring that the configuration files remain unchanged. Detail the specific parameters that were corrected and explain how they impact the task execution. After re-execution, provide a summary of the outcome, including any errors encountered, changes in performance, and whether the desired results were achieved. Format the response in a clear, structured manner with bullet points for easy readability.

Please verify the integrity of the Dockerfile and CI configuration files for [PROJECT NAME]. Check that these files have not been altered from their intended state and provide a detailed report on any discrepancies found. Include information on the original state of the files, the current state, and any specific lines or sections that have changed. Additionally, suggest any corrective actions that may be necessary to restore the files to their intended configuration.

Please execute deployment tests for the CI pipeline to verify that it functions correctly without any errors. Ensure that you cover all critical components of the deployment process, including build integrity, environment configurations, and any integration points with external services. After running the tests, provide a detailed report of the results, including any errors encountered, the status of each test, and recommendations for any necessary fixes or improvements. Format the report in a clear and organized manner, highlighting key findings and next steps.

Please scan the configuration files for [SPECIFIC CONFIGURATION NAME] and identify any unauthorized edits. Provide a detailed report highlighting any unexpected changes that have occurred, including the specific lines or sections that were altered. Additionally, confirm the integrity of the original configuration by comparing it against a known good version. Summarize your findings in a clear format, indicating whether any unauthorized changes were detected and the potential implications of those changes.

Please review the actions outlined in the CLAUDE.md file and validate their compliance with the specified rules. For each rule, provide a detailed assessment of whether it is being followed, including examples or evidence from the actions. If any actions do not comply, specify which rules are violated and suggest corrective measures. Format your response as a compliance report, clearly listing each rule, its status (compliant or non-compliant), and any recommendations for improvement.

Please review the outputs of the recent shell commands executed in the system. Ensure that no configuration files have been altered during these commands. Summarize your findings in a clear and concise report, highlighting any changes detected, the specific files involved, and any potential implications of these changes. Include recommendations for maintaining configuration integrity moving forward.

Help me draft a new rule for my CLAUDE.md file to prevent the recent issue from recurring. The rule should address the specific problem that occurred, outline the rationale behind it, and provide clear guidelines on how to avoid similar situations in the future. Include any relevant examples or scenarios that illustrate the importance of this rule. Format the rule in a way that is easy to understand and implement, ensuring it is concise yet comprehensive.

Please create a detailed pre-task checklist to review before starting any tasks that involve configuration files. The checklist should include key points such as verifying the current configuration settings, ensuring backups are made, confirming access permissions, and reviewing any recent changes made to the files. Additionally, include steps for testing the configuration in a safe environment before applying changes. Format the checklist in a clear, structured manner, with each point numbered for easy reference.

Please suggest a set of naming conventions for configuration files that clearly indicate their significance and discourage unnecessary modifications. The conventions should include specific prefixes or suffixes that denote the purpose and criticality of each file. Additionally, provide examples of how these conventions can be applied to different types of configuration files, such as those for database connections, application settings, and environment variables. Outline the rationale behind each naming choice to ensure clarity and consistency across the project.

Create a guard script that automatically monitors configuration files for unauthorized changes. The script should check for modifications at regular intervals and send an alert to the user if any changes are detected. Include detailed comments in the code to explain the functionality of each section. Additionally, specify the programming language to be used and ensure that the script can be easily integrated into existing systems. Provide the complete code along with instructions on how to run it.

Please add detailed comments to the configuration files that explain the purpose of each section and the specific importance of not altering them without proper approval. Ensure that the comments are clear and concise, making it easy for future users to understand the rationale behind each configuration choice. Additionally, highlight any potential risks or issues that could arise from unauthorized changes. Format the comments in a way that they are easily distinguishable from the code, using a consistent style throughout the file.