Writing perfect code is a challenging process. That’s where code reviews come in to help double check your work.
The code reviewer’s job is to check for business and logic errors in the code changes. Here are simple tips to help the streamline the process.

1. Have the build system that checks if the code changes breaks the build!

Integrate with GitHub: build after each commit (Get started with Jenkins, part 13) – Simply Explained – Savjee

2. Implement a short checklist for all pull requests for both the author AND code reviewers.
Here’s a guide for setting up a pull request template in Github. Tips on creating a good pull request template here.

3. Include a code static analysis tool into the build system.
Here’s a github repo that for the job. -> Awesome Static Analysis