I would recommend reviewing early and initially in smaller blocks to set the standard. Assume you're going to need to read all their code as you're likely goin

I would recommend reviewing early and initially in smaller blocks to set the standard. Assume you're going to need to read all their code as you're likely going to be responsible for passing it (they're only interns). You could pair up, but make sure you still document any questions you have with the code. Systems like Bitbucket are great for commenting against the code and maintaining a record. If it impacts your own productivity address that with your manager so they know why and how much. Give them the opportunity to direct you on how much time you should spend. Don't fix anything or write code corrections yourself, don't waste time if it's clearly unreadable and unmaintainable. Question their code and let them figure it out themselves and you'll find you can get through reviews quickly and effectively. And if you see some great code - acknowledge it!