I suspect automated code reviews and doing high-quality automatic documentation (i.e. better than current standards in most projects) will be fully within the capabilities of LLMs soon. Fixing random build failures will probably follow...

So then the question is what % of a programmers job might be taken by this, and does the remaining % require a different skillset.

There are programmers that are great at coding, but complain loudly when the business gives slightly ambiguous requirements because they see their job as coding, not clarifying business rules. This group are more likely to be impacted than the programmers who will happily work in ambiguous situations to understand the business requirements.