To me this sounds like you and your team mate aren't on the same page when it comes to the level of quality required of the project.
I recently had the same problem with a team. What worked for me was determining the ideal design we all agreed on for every part of the project. The repository would use CQS, the MVC controllers would be very thin and primarily use the services layer etc.
Once every team member agrees on the design of the project, formalize it by, for example, some UML diagrams. Print them so you have them available in the team room during code reviews. When the design is clear, it's easier agree on when good is good enough and more refactoring isn't required.