Yes and no
If "writing code" is a craft then not writing it would result badly reading it, true. But I disagree that software engineering is a "writing code craft", it contains much more (designing system, architecture, testing, requirements and spec design, etc.) so all these things stayed with AI agents writing the code, and also software engineering craft expanded with new workflows and kinds of problems with AI. So getting worse at reviewing the code might be somewhat expected outcome in that change, we'll see over time
It's not really "writing code", and this usage gives it the connotation of "transcribing code". Yes, the things you mention are part of it, but they are still in the realm of plans and not reality.
It's like layers of an onion. Coding is the middle, but there's SO much that goes on around it. Some of these inner layers are getting increasingly solved by AI, but nobody wants the inner layers by themselves, they want the full onion, and more skilled developers will still produce better onions.
There are a lot of skills that are no longer important to software engineering like the specific lines of code that you write, but building software that is maintainable and delivers value to its users involve many many more skills than LLMs can deliver right now.
If you want to stay relevant in the field, there is no way forward other than embracing the torrent of LLM tools, news, releases, and figuring out how to shape that into your process in a reliable and responsible way.