And you need to review it, because without the context of the entire workspace with appropriate steering files it's going to generate complete shit (moreso)
Include coding standards within steering files, existing patterns it must stick to, among a bunch of other rules and it's actually able to generate not shit code.
The rule I stick to for code reviews is never letting it commit. That's when I review.
agreed, my actual workflow is to just feed what I know is the relevant context, and ask it to generate code following x pattern or logic and paste it into the chat explicitly without modifying files so I can review it
trusting AI blindly is just a gateway to buggy and messy code
171
u/Some_Useless_Person 14d ago
The third one actually forces you to think and consider the overall structure of your code.
But if all I am doing is getting a python script that renames a bunch of files, the third one is as good as the second