Yes, except it's "bad automation", because as opposed to the automation referred to by GP, boilerplate written by an LLM (or an intern or whomever) is extra code that costs a lot of time to be maintained.

In many ways it's more akin to outsourcing then automating.

And might be wrong.

But, perhaps uniquely amongst all the systems for avoiding boilerplate since Lisp macros were introduced in the 1950s, it will sometimes make stuff up. I don't buy that "a worse way to write boilerplate" is going to revolutionise programming.