In other words, technical debt is when parts of the system does not yet implement the abstractions that align with the developers understanding of the problem?

In other words, technical debt is when parts of the system does not yet implement the abstractions that align with the developers understanding of the problem? While I don't think we're there yet or maybe not even close, I kind of feel like this kind of technical debt would be something that an LLM should be able to help with. Why can't I point to a piece of code and say "Look at this new code I wrote, now go and refactor the rest of the code base to align with it." Or can I? I assume if I tried to implement something that did this I would hit the context size limit and that would be it.