AI Prompts for Preventing Config File Modifications

Please help me identify the configuration files that have been modified in my project. I will provide a list of file names: [PASTE FILE NAMES]. Analyze these files and determine which ones have been altered in the last task. Additionally, provide a brief summary of the changes made to each affected file and any potential impacts these changes may have on the overall configuration.

Please provide a detailed report on the recent changes made to the Dockerfile, GitHub Actions, and CI pipeline configuration files. Include a summary of each change, specifying the date and author of the modification. Highlight any unexpected modifications and explain why they may be considered unexpected, along with potential impacts on the project. Format the report in a clear, organized manner with bullet points for each file and change.

Please summarize the last five tasks executed in your project, detailing the specific actions taken and their outcomes. Identify any task that may have triggered recent configuration changes, explaining the potential impact of those changes on your current setup. Additionally, provide insights into how these tasks relate to the overall project goals and any challenges faced during execution. Format your response as a structured report with clear headings for each task and its analysis.

Please analyze the error logs from the last build and identify any entries that indicate issues with configuration files. Summarize the key errors found, including the specific lines or messages that highlight the problems. Additionally, provide recommendations on how to resolve these configuration issues based on the errors detected. Format your response as a detailed report with sections for each error and suggested fixes.

Please confirm whether there have been any internal iterations on configuration files during the last task. If iterations occurred, provide a detailed list of each iteration, including the specific changes made, the rationale behind those changes, and the outcomes or results of each iteration. Additionally, describe how these iterations impacted the overall task and any lessons learned that could inform future configurations.

Please apply a lock on the following configuration files: Dockerfile, GitHub Actions, and CI pipeline configuration files. Ensure that these files are secured against any further modifications. After applying the lock, confirm the status of the lock for each file, providing details on whether the lock was successful and any relevant information regarding the locking process. Additionally, outline any steps that may be required to unlock these files in the future.

Please revert any unintended changes made to the configuration files during the last task. Provide a detailed list of the specific files that were altered, along with a summary of the changes that have been reverted. Additionally, include the original content of the files before the changes were made for comparison. Ensure that the output is clear and organized, making it easy to understand what was reverted and why.

Please modify the internal logic of the system to ensure that configuration files are excluded from automatic iterations. Provide a detailed explanation of the changes made to the logic, including any specific conditions or parameters that were adjusted to achieve this exclusion. Additionally, confirm that the exclusion has been successfully implemented and outline any potential impacts this may have on the overall functionality. Finally, include any necessary steps for testing the changes to ensure they work as intended.

Please help me develop a patch for the configuration handling process to prevent unwanted modifications in the future. The patch should include specific changes to the code that enhance security and integrity, as well as detailed comments explaining each modification. Additionally, provide a confirmation method to ensure the patch has been successfully applied and is functioning correctly. Outline the steps involved in testing the patch to verify that it effectively prevents unauthorized changes.

Please re-run the last task while applying specific constraints on modifications to the configuration file. Clearly outline the constraints you are implementing, and provide a detailed report of any changes made during this process. Include information on how these changes affect the overall functionality and performance of the system, and suggest any further actions that may be necessary based on the results of this re-run.

Please verify the integrity of the following files: Dockerfile, GitHub Actions configuration, and CI pipeline configuration files. Check each file for any modifications or changes since the last confirmed version. Provide a detailed report that includes the status of each file (intact or modified), the date of the last change if applicable, and any discrepancies found. Additionally, suggest steps to rectify any issues identified during the verification process.

Please execute a test deployment using the current configuration files to verify that they are functioning correctly. Ensure that no modifications are made to the files during this process. Provide a detailed report on the deployment results, including any errors encountered, the status of each component, and recommendations for any necessary adjustments. Additionally, include a summary of the overall deployment performance and any areas that may require further testing or attention.

Please validate the lock mechanism on configuration files to ensure it is both active and effective. Conduct a thorough check to determine if the mechanism is functioning as intended, and identify any potential issues or areas for improvement. In your status report, include details such as the current status of the lock mechanism, any discrepancies found, and recommendations for enhancing its effectiveness. Format the report in a clear and concise manner, summarizing your findings in bullet points for easy reference.

Please analyze the latest build logs for the project. Identify and highlight any configuration file errors or discrepancies present in the logs. Provide a summary of the findings, including the specific lines or sections where issues were detected, and suggest possible resolutions for each discrepancy. Format the output in a clear, organized manner, making it easy to understand the nature of the errors and the recommended actions to take.

Please confirm whether the constraints applied during the task execution are effectively preventing any unwanted configuration changes. Provide a detailed analysis of the specific constraints in place, how they are being enforced, and any instances where configuration changes were attempted but blocked. Additionally, include recommendations for improving the constraint enforcement process if any gaps are identified.

Draft a new rule for CLAUDE.md aimed at preventing unauthorized modifications to configuration files. The rule should clearly outline the specific actions that are prohibited, the rationale behind these restrictions, and the consequences for violations. Additionally, include guidelines for how team members should handle requests for changes to configuration files, ensuring that there is a formal review process in place. Format the rule in a clear and concise manner, suitable for inclusion in the CLAUDE.md document.

Please insert detailed comments in the configuration files that explain the importance of not modifying them. Each comment should clarify the potential consequences of changes, such as instability or security risks, and provide guidance on when modifications may be appropriate. After adding the comments, show me the updated configuration files with the comments included, ensuring that the explanations are clear and informative for future reference.

Create a detailed checklist for session openers to ensure that configuration files remain unaltered during the session. The checklist should include specific actions to take before starting the session, such as verifying the integrity of the configuration files, confirming that backups are in place, and ensuring that all team members are aware of the importance of maintaining file integrity. Additionally, include steps for monitoring changes during the session and procedures for reporting any unauthorized modifications. Format the checklist in bullet points for easy reference.

Propose a comprehensive naming convention for configuration files that ensures easy identification and protection from unauthorized modifications. The convention should include specific prefixes or suffixes to denote the purpose and sensitivity of each file. Provide at least five examples of naming conventions, explaining the rationale behind each choice and how it contributes to better organization and security of the configuration files. Additionally, outline any best practices for maintaining consistency in naming across different environments or projects.

Please help me implement project guards to monitor and alert on any changes to configuration files in my project. I need a detailed plan that includes the specific types of configuration files to monitor, the criteria for triggering alerts, and the methods for confirming that the guard setup is functioning correctly. Additionally, outline the steps for testing the guard system to ensure it effectively detects unauthorized changes. Provide this information in a structured format that I can follow easily.