I have been using Composer heavily since it was released and this prompt is what I have been using when debugging tests/errors:
I'm working on a TypeScript project and encountering multiple errors and failing tests. Please identify the most critical errors that are likely causing cascading issues, determine specific code changes to resolve these errors, starting with the most impactful ones. Then explain the root cause of each error, why the suggested fix addresses it, and then fix the errors yourself by editing the files directly. If you need to see any specific code files to provide more accurate suggestions, please let me know.
I have tried further optimizations with o1-preview and Claude Sonnet 3.5 to improve this prompt, but I have found it already tends to produce the best code, avoids “churning” through the same errors, and actually applies changes to the files instead of outputting it to the Composer chat window. However, I’m curious about what other people are using for debugging.