In a straight forwards repo with no README it created a reasonable starting point.
Yet in a more complex repo with an existing and comprehensive README, it decides to replace it completely with a simple one, removing key insights. I suspect the existing README isn't considered at all, making this kind of patch incompatible with most workflows (i.e. creating a README once isn't particularly onerous, keeping it up to date is).
This may be a project to watch, but I'm disinclined to use it at the moment.
Thanks for trying - and for the fair feedback! We'll look at the AutoFix result and improve it.
Our goal with the default patchflows is to provide a starting point/template and let you tailor it to your needs from there. E.g. with the 'Generate README' workflow, you can add the 'Read File' step to read the existing file and pass it to the context to update it rather than generate a new one from scratch.
For a simple PoC typescript CLI tool I had, AutoFix decided to do this several times:
https://i.postimg.cc/1z4Fs663/Screenshot-2024-10-31-at-21-37...
In a straight forwards repo with no README it created a reasonable starting point.
Yet in a more complex repo with an existing and comprehensive README, it decides to replace it completely with a simple one, removing key insights. I suspect the existing README isn't considered at all, making this kind of patch incompatible with most workflows (i.e. creating a README once isn't particularly onerous, keeping it up to date is).
This may be a project to watch, but I'm disinclined to use it at the moment.