I'm trying to figure out ways to placate the boss by fitting AI into the edges of my workflow. "Look at these commits and do a review" to find stupid stuff lik

I'm trying to figure out ways to placate the boss by fitting AI into the edges of my workflow. "Look at these commits and do a review" to find stupid stuff like forgotten exception throws or nulls. Or "Critique this documentation for a different audience" I don't want to get into the "let the machine write the code" phase because that's the task I enjoy most, and it swaps my efforts into review, which I'm bluntly less confident about (having to follow and second-guess an architecture without being "there" when it was evolved increases the chances I'll miss stuff) The stuff that AI demos well at-- "refactor 5,000 lines of code", "build a new client from ground level" are simply not what my team works on; we end up doing things where building a prompt to actually make the change we want-- and only the change we want-- takes longer than writing the code itself. 80% of the time is the debugging and planning.