Replace long PR comment threads with clear, visual code review recordings. Walk through diffs, explain concerns, and share context faster than text.
Code review comments often miss the mark because they lack context. A comment saying 'this might cause a race condition' doesn't convey the same urgency as walking through the code and showing exactly where and how the issue occurs. Video code reviews add the nuance that text reviews miss, and they're faster to create than writing detailed comments.
Follow these steps for the best results.
Open the pull request on GitHub, GitLab, or your code review tool in Chrome. Switch to the 'Files changed' view so you can see the diff. If the PR is large, open specific files you want to discuss rather than scrolling through the entire diff.
Decide whether to review file by file or by concern. For small PRs, go file by file. For larger PRs, group your feedback by theme: 'First, let's look at the architecture concern, then the performance issue, then some style suggestions.' This structure makes your review easier to follow.
Start Zumie and record the browser tab showing the diff. Click on specific lines of code as you discuss them. Zumie's auto-zoom magnifies the code around your cursor, making variable names, function signatures, and logic clearly readable in the recording.
Don't just say 'change this variable name.' Explain why: 'This variable is called data but it's actually a list of user sessions — renaming it to userSessions makes the function's purpose clearer when someone reads it later.' Context prevents the same mistakes in future PRs.
Post the Zumie link as a PR comment. Include a brief text summary of your key points so the author can prioritize. The video provides the detailed context; the text comment provides the quick reference.
Level up your results with these expert techniques.
Start with something positive about the code. Frame suggestions as questions: 'Have you considered using a map here instead of a loop?' This tone works better on video where your voice carries the nuance that text misses.
Click on line numbers as you reference them. Zumie's auto-zoom will center on that line, and the line number itself becomes visible. This makes it easy for the author to find exactly what you're discussing when they go back to the code.
If you have both architectural concerns and minor nitpicks, record two separate videos. The author can prioritize the important video first and address minor feedback when they have time.
A 20-minute code review video is overwhelming. If the PR is large, break your review into multiple focused videos (3-5 minutes each) covering different aspects. The author can address each one independently.
Talking about code without pointing to specific lines forces the author to guess what you mean. Always click the exact line you're referencing so the auto-zoom centers on it and the line number is visible.
Don't just say 'this is wrong.' Show an alternative approach or explain the pattern you'd suggest. Video reviews that only point out problems without solutions are demoralizing and unhelpful.
Watch how Zumie's auto-zoom and click highlights transform a basic screen recording into a polished, professional video.
For complex feedback that requires context and explanation, video is usually 2-3x faster to create than writing detailed comments. For simple one-line suggestions, text comments are faster. Use video for the nuanced stuff.
Yes. Navigate to specific commits in the PR view before recording. Zumie captures whatever is on your screen, so you can show commit-by-commit diffs or the overall PR diff — whatever best supports your review.
Video reviews are perfect for async teams. Record your review, post the link, and the author watches it during their working hours. They can pause, rewatch complex sections, and respond when ready. No scheduling needed.
Install Zumie for free and create your first professional recording in minutes. No signup, no credit card, no commitment.
See how Zumie works with specific tools.