try using a harness. i provide one in Yaw Mode and you can copy it and modify and use a modified if you wanted to learn and tweak yours.

i use the skills /yaw-review excessively sometimes multiple times in a row on the same pr or session. followed by most often /yaw-address-all and then /yaw-coverage to add tests and /yaw-ship-ready to make production ready.

after a few rounds of these they are not needed every time on the same codebase.

if you are desperately wishing programming to go back to the before times it will never. or it will always be there but expect to be incredibly less productive than your peers.

You are not suggesting harness will replace the need of programmer's review aren't you? The thing might go in the totally wrong direction and no harness will stop it. Surely unless you write harness for every specific task at hand but then why is it any better than writing or at least reviewing the code itself?