My thoughts around code quality are generally that if you're writing code for yourself (as a hobby, for open source, whatever) -- then write code however you want, as it's for fun. Obviously, others can contribute fixes and help make things better, but there's no professional "responsibility" in these cases.
On the other hand, if you're writing software meant to be used by others (including companies you work for), it's your responsibility as a developer to ensure the code you're pushing is:
- In compliance with style conventions
- Properly reviewed for security issues (tools like Snyk and other SAST/SCA tools work well for this)
- Makes architectural sense given the rest of your codebase
- Is documented so others can easily contribute/review without a lot of handholding
The rules above are true regardless of how the code is being generated.