AI Prompts for Preventing Unwanted Config Changes

Please provide a comprehensive list of all the files that were modified during the last task. For each file, include specific details about the changes made, particularly focusing on any alterations to the Dockerfile, GitHub Actions, or CI pipeline configuration files. Additionally, summarize the purpose of each modification and how it impacts the overall project. Format your response in a clear, organized manner, with sections for each type of file and a brief explanation of the significance of the changes.

For each modified configuration file, provide a detailed explanation of the reasons behind the changes made. Include whether these modifications were essential for achieving the task at hand and how they contribute to the overall functionality or performance. Additionally, discuss any potential alternatives that were considered and why the chosen modifications were preferred. Format your response as a structured list, with each file clearly labeled and the rationale for changes outlined in bullet points.

Please review the contents of my CLAUDE.md file: [PASTE CONTENT]. Analyze each rule outlined in the document and confirm your understanding of them. After your review, identify which specific rule was applicable to the last task I assigned and explain how it should have been applied. Provide a summary of any compliance issues you found and suggest ways to ensure adherence to the rules in future tasks.

Identify and describe any unintended changes made to the configuration files during the setup process. For each change, specify the exact file that was affected, the nature of the modification, and the potential impact it may have on the overall system functionality. Additionally, provide a brief explanation of how these changes occurred and any steps that can be taken to revert them or mitigate their effects.

Please assess the impact of the changes made to the configuration files in the context of our project. Detail any build or deployment issues that arose as a result of these changes, including specific error messages or failures encountered during the process. Additionally, explain how these issues affected the overall functionality of the application and any steps taken to resolve them. Provide a summary of lessons learned and recommendations for future configuration changes to avoid similar issues.

Please review the Dockerfile, GitHub Actions, and CI pipeline configuration files for any unintended changes. Identify and revert any modifications that do not align with the original intended state. After making the necessary corrections, provide a summary of the changes that were reverted and confirm that the files are now restored to their original configurations.

Please restore the previous configurations for the affected files to the last known good state. After completing the restoration, confirm that the files have been successfully reverted and provide a summary of the changes made. Additionally, outline any potential impacts this restoration may have on the current setup and suggest any further actions that may be necessary to ensure stability.

Please review the configuration files and reapply the correct rules as outlined in the CLAUDE.md document. Ensure that each rule is accurately implemented and that the configuration adheres to the specified guidelines. After applying the rules, provide a summary of the changes made and confirm that the rules are now correctly applied. If any discrepancies are found, highlight them and suggest necessary adjustments.

Please validate the integrity of the Dockerfile, GitHub Actions, and CI pipeline configuration files for my project. Check for any syntax errors, missing dependencies, or misconfigurations that could prevent successful builds or deployments. Provide a detailed report on any issues found, including suggestions for fixes and best practices to ensure the configurations are functional and optimized. Additionally, confirm that the configurations align with industry standards for security and performance.

Review the configuration files for [PROJECT NAME] to ensure that only task-specific changes are included. Identify and list any unrelated modifications that may have been made, providing a brief explanation for each. Additionally, suggest how to revert or correct these unrelated changes to maintain the integrity of the configuration. Format your findings in a clear report with sections for task-specific changes and unrelated modifications.

Please run a series of configuration tests on the Dockerfile, GitHub Actions, and CI pipeline configuration files to verify their functionality. Ensure that each component is tested for common issues such as syntax errors, dependency resolution, and execution flow. After completing the tests, provide a detailed report of the results, including any errors encountered, warnings, and a summary of successful configurations. Format the report clearly, highlighting areas that may need attention or improvement.

Please review the configuration files for [PROJECT NAME] to identify any syntax or logical errors. Provide a detailed analysis of each file, highlighting any issues found and suggesting corrections. Additionally, confirm that all configurations are set correctly and functioning as intended. Include a summary of your findings and any recommendations for improvements or best practices moving forward.

Please verify the success of the build process using the current configurations. Start by triggering the build and monitor the output for any errors or warnings. Once the build is complete, provide a detailed report on the build status, including any issues encountered, the time taken for the build, and whether all expected outputs were generated successfully. If there are errors, please list them along with possible solutions or next steps to resolve the issues.

Please check the deployment status of the application that has been configured with the current settings. Verify that the deployment was successful by providing details on any errors or issues encountered during the process. Additionally, confirm that the application is fully functional by testing key features and functionalities. Summarize your findings in a report format, including any recommendations for improvements or adjustments if necessary.

Please review all configuration files and validate that they comply with the rules outlined in the CLAUDE.md document. Provide a detailed report highlighting any discrepancies or areas of non-compliance, including specific sections of the configuration files that do not meet the established rules. Additionally, summarize the overall compliance status and suggest any necessary changes to ensure full adherence to the guidelines. Format the report clearly, with sections for compliant files, non-compliant files, and recommendations for adjustments.

Based on the recent issue I encountered with [SPECIFIC PROBLEM], help me formulate a new rule to add to my CLAUDE.md file that will prevent this from recurring. The rule should clearly outline the steps to avoid similar mistakes in the future, including any specific configurations, checks, or best practices that should be followed. Please provide the exact text I can copy and paste directly into my CLAUDE.md, ensuring it is concise yet comprehensive enough to be easily understood and implemented.

Please add detailed comments to the configuration files for [SPECIFIC CONFIGURATION FILES]. Each comment should explain the purpose of the corresponding section and highlight any critical rules or considerations that need to be noted. Ensure that the comments are clear and concise, making it easy for someone unfamiliar with the configuration to understand its functionality. Format the comments in a way that they can be directly inserted into the files, and provide examples where necessary to illustrate complex rules or settings.

Please develop a comprehensive session-opener checklist to review before starting a session focused on protecting configuration files. The checklist should include at least ten specific items that cover aspects such as verifying file permissions, ensuring backups are up to date, confirming access controls are in place, and checking for any recent changes to the configuration. Additionally, include steps for reviewing the security settings of the environment and any necessary documentation that should be consulted. Format the checklist in a clear, easy-to-follow manner.

Help me establish clear and effective naming conventions for configuration files related to [SPECIFIC USE CASE OR PROJECT]. The conventions should ensure that files are easily identifiable and protected from accidental changes or deletions. Include guidelines on how to structure names, such as using prefixes or suffixes that indicate the file's purpose, versioning, and environment (e.g., development, testing, production). Additionally, provide examples of good naming practices and any potential pitfalls to avoid in order to maintain consistency and clarity across the project.

Help me implement project guards to prevent unintended modifications to configuration files in my project. I need a comprehensive list of strategies or settings that can be applied, including specific tools or methods to enforce these guards. Please include detailed instructions on how to set up each guard, what configurations to apply, and any potential pitfalls to watch out for. Additionally, provide examples of how these guards can be tested to ensure they are functioning correctly.