AI Prompts for Preventing Unwanted Config Changes

Please identify all the configuration files that have been modified during this session. For each file, provide a detailed summary of the specific changes made, including the original content and the modifications. Additionally, explain the purpose of each file and how the changes may impact the overall configuration. Format the response in a clear list, with each file's name as a heading followed by the details of the changes.

Please provide a summary of the last five changes made to my project. Focus specifically on modifications related to the Dockerfile, GitHub Actions, and any CI pipeline files. For each change, include the date it was made, a brief description of the modification, and the potential impact it may have on the project's functionality or deployment. Format the information in a clear and organized manner, making it easy to review the recent edits.

Please review the following .cursorrules file: [PASTE CONTENT]. Confirm whether the rules outlined in this file are being adhered to and identify any discrepancies or areas of non-compliance. Additionally, provide suggestions for how to address any issues you find, including specific examples or changes that could be made to ensure compliance with the rules. Summarize your findings in a clear and structured format.

Please provide a detailed analysis of the context surrounding your decision to modify the configuration files. Describe the specific task you were attempting to complete, including the goals you aimed to achieve and any challenges you faced during the process. Additionally, explain any relevant background information that influenced your decision, such as previous experiences, project requirements, or technical constraints. Your response should be structured in three to four paragraphs to ensure clarity and depth.

Identify any dependencies or related files that may have triggered changes in the configuration files for the project. Please analyze the configuration files and provide a detailed list of these dependencies, including their file paths and any relevant version information. Additionally, explain how each dependency is related to the configuration changes and the potential impact on the overall system. Format the output as a structured report with headings for each dependency and a brief description of its role.

Please revert the unwanted changes made to the Dockerfile, GitHub Actions, or CI pipeline files during this session. After reverting, summarize the specific changes that were undone, including the original state of the files and the modifications that were removed. Ensure that the summary is clear and concise, highlighting any potential impacts these changes may have had on the overall project. Additionally, provide recommendations for best practices to avoid similar issues in the future.

Please lock the following files from further modifications during this session: Dockerfile, GitHub Actions configuration, and CI pipeline files. After locking these files, confirm the lock status and provide a brief summary of the locking process. Ensure that no changes can be made to these files until the session is completed.

Please apply the correct rules from the .cursorrules file to the current task. Ensure that the application of these rules does not result in any alterations to the configuration files. Provide a detailed summary of the rules applied, including any specific considerations or exceptions that were taken into account during the process. Additionally, outline any potential impacts on the task's execution and suggest best practices for maintaining the integrity of the configuration files moving forward.

Please restore the previous version of the configuration files from the last known good state. After restoring, provide a detailed summary of the changes made, including the names of the restored files, the specific configurations that were altered, and any potential impacts these changes may have on the current setup. Additionally, include any recommendations for future configuration management to prevent similar issues. Format the summary in a clear, organized manner for easy reference.

Identify the specific task that led to the configuration changes in the Docker or CI setup. Explain the steps taken to isolate this task and ensure that it does not impact other files or processes. Include details on the methods used for isolation, any challenges encountered, and how they were resolved. Finally, provide a summary report of the entire isolation process, highlighting key findings and recommendations for future configurations.

Please verify the integrity of the following files: Dockerfile, GitHub Actions configuration, and CI pipeline files. Check the last modification dates against the last fix to ensure that no unauthorized changes have been made. If any files have been modified, provide details on which files were altered and the nature of the changes. If everything is intact, confirm that all files remain unchanged since the last fix.

Please execute a series of tests on the configuration files to verify their functionality. Ensure that each configuration is tested against expected outcomes and document any discrepancies or issues that arise during the testing process. Provide a summary report detailing the results of the tests, including specific configurations that passed, those that failed, and any recommendations for resolving the identified issues. The report should be structured with clear headings for each configuration tested and a conclusion summarizing the overall status.

Check the current session against the rules defined in the .CURSORRULES file. Provide a detailed compliance status report, including any rules that are not being followed and suggestions for how to achieve compliance. Additionally, summarize the implications of non-compliance and recommend best practices to ensure adherence to the rules in future sessions. Format the response clearly, highlighting key findings and actionable steps.

Please validate the completion of the task that previously caused the issue. Ensure that the resolution did not impact any configuration files. Generate a detailed task completion report that includes: a summary of the task, the steps taken to resolve the issue, any changes made to the configuration files (if applicable), and confirmation that the system is functioning as expected. Format the report in a clear and organized manner, suitable for sharing with the team.

Please conduct an audit of the recent sessions to identify any unauthorized changes made to configuration files. The report should include details such as the date and time of each session, the user responsible for the changes, a description of the changes made, and any potential impact on system integrity. Additionally, summarize any patterns or recurring issues found during the audit. Format the report as a structured document with clear headings for each section.

Draft a new rule for the .cursorrules file that will prevent unwanted changes to configuration files in our project. The rule should specify the types of changes that need to be restricted, including any specific file extensions or directories that should be monitored. Include clear conditions under which changes are allowed and outline the actions that should be taken if a violation occurs. Please provide the exact text of the rule formatted correctly for the .cursorrules file.

Create a comprehensive checklist to be used at the start of each session to ensure that configuration files are protected. The checklist should include items such as verifying access permissions, ensuring backups are up to date, checking for recent changes to configuration files, confirming that security protocols are in place, and reviewing any recent incidents or alerts related to configuration security. Format the checklist as a numbered list with clear, actionable items that can be easily followed.

Please insert comments into the configuration files that explain the importance of not altering them without explicit permission. The comments should clearly outline the potential consequences of unauthorized changes, including risks to system stability and security. Additionally, provide guidance on how to seek permission for modifications and emphasize the importance of following established protocols. Format the comments in a way that is easy to read and understand for anyone who may work with these files in the future.

Propose a comprehensive naming convention for configuration files that clearly indicates their importance and immutability. The convention should include specific guidelines on how to structure the names, such as using prefixes or suffixes that denote the file's purpose and stability. Additionally, explain the rationale behind the chosen naming elements, including any best practices for maintaining consistency across different environments. Finally, provide examples of configuration file names that adhere to this convention to illustrate its application in real-world scenarios.

Design a project guard mechanism that alerts users when configuration files are about to be modified. Include specific details on how the guard will function, such as the types of modifications it will monitor, the criteria for triggering alerts, and the method of notification (e.g., email, in-app message). Additionally, outline the steps for implementing this guard within a project, including any necessary configurations or dependencies. Ensure the solution is scalable and can be adapted for different project environments.