AI Prompts for Diagnose Silent Build Failures

Please provide the last build output from your project, focusing on the section that details the commands executed. Highlight any discrepancies you observe between the executed commands and the expected commands. Additionally, summarize any potential reasons for these discrepancies and suggest steps to resolve them.

Please analyze the complete build log pasted below: [BUILD LOG]. Identify any warnings or errors that may not have been displayed in the interface. Provide a summary of your findings, including the specific issues detected and suggestions for resolving each one.

Please explain your understanding of the build process based on the instructions provided. Include details about the key steps involved, what the expected outcome should be, and any potential issues you foresee that could lead to a silent failure. Format your response as a structured outline, highlighting each step and its significance in achieving the desired result.

Compare the expected build behavior with the actual build behavior for the project on [PLATFORM/TOOL NAME]. Detail the expected output of the build process, including any specific features or functionalities that should have been present. Then, outline what actually occurred during the build, highlighting any discrepancies, errors, or unexpected results. Format your response in a table with columns for "Expected Behavior" and "Actual Behavior," and provide a brief analysis of potential causes for any differences observed.

Please analyze the build process and identify any specific rules or constraints that were violated. For each violation, quote the exact clause that was not adhered to and provide a brief explanation of how it impacted the build. Format your findings in a structured list, including the rule, the violation, and its implications.

Please revert the function signature at src/app.js:42 back to its original form, which is function myFunction(param1, param2). Before you apply this change, provide a detailed diff showing the differences between the current signature and the original. Include the line numbers affected and ensure the output is clear and easy to understand.

Please rewrite the configuration file in config.json to include the required fields 'databaseUrl' and 'apiKey'. Use the correct values for these fields based on the current project requirements. Ensure that no other changes are made to the existing configuration, and provide the updated JSON structure in a formatted manner.

Please update the environment variable 'DB_CONNECTION_STRING' to 'mongodb://localhost:27017/mydb' in the configuration settings. Ensure that no other environment variables are modified during this process. After making the change, confirm that the new value is correctly applied and functioning as intended.

Reformat the code in the file [FILE PATH] according to the project's ESLint configuration. Provide a detailed list of all changes made, including specific lines that were altered and the reasons for each modification. Ensure that the reformatted code adheres to the specified formatting rules and is ready for review.

Please review the import statements in the file server.js. Specifically, change the line 'import express from 'express';' to 'const express = require('express');'. After making this change, confirm that the import is functioning correctly by checking for any errors during runtime and ensuring that the express module is accessible in the application.

Please execute a test build for the project and confirm whether it completes successfully. Report any output messages, focusing particularly on errors or warnings that may arise during the build process. Provide a summary of the build status, including any issues encountered and suggested steps for resolution.

Please provide the diff of the changes made to [FILE PATH] for the purpose of verifying the resolution of the build failure. Highlight only the necessary modifications that were applied, ensuring that no other parts of the file were altered. Format the output to clearly indicate the lines added and removed, and include a brief explanation of the significance of each change.

Replay the original build scenario that failed in [PROJECT NAME] and confirm whether the same failure occurs or if the issue has been resolved. Please provide a detailed report on the steps taken during the replay, the outcome of the build process, and any error messages or logs generated. Additionally, include any observations that may help identify the cause of the failure or confirm its resolution.

Please test the edge case of [EDGE CASE DESCRIPTION] that previously caused the build to fail. Confirm if this edge case still results in a failure or if it has been resolved. Provide a detailed report on the outcome, including any error messages received, the steps taken during testing, and suggestions for further action if the issue persists.

Please verify the output state after the build process for [PROJECT NAME]. Confirm that the expected files, such as [EXPECTED FILES], are generated successfully and ensure there are no residual errors in the output logs. Provide a summary of your findings, including any discrepancies or issues encountered during the verification.

Please implement a pre-build validation check for the project. Before initiating any build step, verify the presence of the files 'src/app.js' and 'config.json'. If either file is missing, stop the build process and alert the user with a clear message indicating which file is missing. Ensure that the build does not proceed without these essential files.

Please create a self-check request that runs prior to deployment for the project. The request should verify that all required environment variables are set. If any variables are missing, the process should stop and notify the user with a clear message indicating which variables need to be addressed before proceeding.

Please create a comment guard in the package.json file that ensures all dependencies are correctly listed and that their versions are compatible. If any discrepancies are detected, the guard should alert the user before the installation process begins. Provide a code snippet that demonstrates how to implement this functionality effectively.

Create a project convention message for the build process that emphasizes the importance of running tests before initiating a build. The message should state: 'Always run tests before initiating a build. If tests fail, do not proceed with the build process.' Ensure the message is clear and concise, and suggest a method for displaying it prominently in the build pipeline.

Please create a detailed instruction for logging build errors in a software project. The instruction should specify that all build errors must be recorded in a file named [FILENAME], which should be easily accessible for review. Additionally, include steps on how to check this file for detailed error messages in the event of a build failure, ensuring that developers can quickly diagnose and address issues.