
Use Gemini's window-sharing to document code reviews faster
You'll have a library of annotated code review notes with visual context automatically captured, ready to share with your team.
What you'll make
Code Review Documentation Library
- Review Session Notes: date, files, and key decisions
- Pattern Catalog: recurring issues with visual examples
- Team Feedback Templates: reusable review structures
Paste your organized notes with Gemini-generated annotations and visual references
The 2 parts
Each part ends with a check you can see.
Test Screen Capture Accuracy
Evaluate how well Gemini's window-sharing captures technical context from your actual code reviews.
Done when
You have 3+ documented review sessions where you've marked what Gemini got right vs wrong about the technical content.
Design Team-Specific Templates
Create documentation templates that work for your team's actual review workflow and technical standards.
Done when
You have 3+ review templates tested with real reviews that capture what your team actually needs to document.
Capstone: you put together your Code Review Documentation Library.
Where this helps
An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.
About this lesson
What you'll be able to do
- Capture and annotate code reviews using Gemini's window-sharing feature
- Build a searchable library of code review notes with visual context
- Document recurring code patterns and team feedback efficiently
Who it's for
- Software developers who review code regularly
- Team leads who need to document review feedback
- Engineers working on distributed teams who want better async code review documentation
What it won't cover
- Code review best practices or methodology
- Setting up version control workflows
- Team communication tools beyond documentation
Skills you'll practise
- Visual documentation capture
- Technical context evaluation
- Template design and testing