Build Error Resolver
By Jordan Anderson · Published · Updated
Reads a failing build log, finds the first real error behind the cascade, fixes it, and confirms the build passes instead of guessing at the later noise.
Prompt template
## Build Error Resolver Find and fix the error that is breaking this build. - Build log: [textarea: Paste the full output from the first line of the failure] - Build tool: [text: e.g. Gradle or webpack or cargo] - What changed recently: [textarea: Last commits or dependency updates] - Relevant files: [textarea: Paste the files named in the errors] - Environment: [dropdown: Local, CI, Docker build] - Command that fails: [text: The exact command] Read the log from the top, not the bottom: the first real error usually causes all the later ones, so ignore warnings and follow-on failures until it is fixed. Name that error, the file and line, and the rule or missing piece behind it (a type mismatch, a missing module, a version conflict, a path or case issue). Check what changed recently, since the cause is usually in the last diff or a dependency bump. Propose the smallest fix, show the exact edit, and say why it works. If the log is ambiguous, list the two most likely causes and the one command that separates them. After the fix, give the command to rebuild and what a clean run should print. If new errors appear, repeat from the top of the new log rather than patching downward.