why would you think not with XP ? If you're doing pair programming then you could argue that the code review happens immediately
Automated code reviews can also happen quickly in an Agile enviromnent, there's usually a build server that is continiously building from the latest sources and one of the builds tasks can be to run some automated code checks
Agile doesnt mean that all processes go out of the window, on the contrary it should be a very controlled process
As Phil says, agile IS a very controlled process, just like other processes.
BUT, what agile says is that if the process isn't working, go ahead and change it as required to make it work, as opposed to traditional processes where you are lockstepped to the process and phase you are in.
The other difference is that agile recognizes that the further out you plan, the less certain you can be about things. Compare and contrast to iterative or waterfall, where the assumption is that you can plan the entire project at the beginning.
Other than that, agile is very similar to other processes. You still do requirements elicitation. You still do architecture. You still do development. You still do QA. You just have "permission" to change process things that aren't working.