Repo Mastery
Study the change.
Read the touched areas, important flows, and decisions. Connect the summary to the evidence behind it.
Start with: What changed, and why?
A field guide to the code you work with
Know the code.
Explain the
decisions.
Reading a codebase is a start. Build a working understanding of what changed, why it matters, and how you would defend the tradeoffs.
Try a sample changeFree for individuals. Start with a sample repository.
01 / Read with a purpose
02 / Question your assumptions
03 / Explain it in your own words
The method
Turn a walkthrough into
working knowledge.
Follow a change from its intent to its consequences. Then find out which parts you can explain without leaning on the summary.
Test your understanding.
Work through questions about intent and risk. Revisit the parts you could recognise but could not yet explain.
Ask: What could I be missing?
Make the case yourself.
Practise the explanation, identify the tradeoff, and keep evidence of the learning work you completed.
Explain: What would I check next?
For the work ahead
A useful explanation
should survive a question.
A summary helps you get oriented. Guided practice helps you discover whether you understand the system well enough to work on it.
When you inherit a repository.
Build your own map of its responsibilities, entities, and critical flows. Use questions and recall to decide what to investigate next.
When you need to own a change.
Review the intent and risks before a handoff or design review. Be clear about what you understand, what you checked, and what remains uncertain.
Access
Make learning the easy decision.
For individual engineers
Free.
The individual learning experience is free, including your own public and private repositories. No individual subscription or payment card required.
- Repository walkthroughs, questions, and recall practice
- Change Mastery and Reality Checks
- Unlimited individual repositories
- Learning evidence, certificate, and proof export
For teams / Early access
Understand where your team needs support.
Shared coverage, seats, administration, and cross-repository reporting are the team direction. Join the early-access list for updates as plans open.
Submitting sends your email to our form provider, Formspree, for team updates.
You're on the list. We'll email you about team early access.
Read the plan details →The right tool for the next task
Connected by your work.
Use Repo Mastery on its own, or continue with a tool that fits what you need next. Starting here does not require an OpenThunder download.
OpenThunder / Inspect & build
Need to work on the code itself?
Explore the repository, build with context, and inspect the checks behind a change. Choose the desktop app or Cloud.
Download or try OpenThunder Cloud ↗Skills Tech Talk / Practise & communicate
Need to explain it under pressure?
Practise communicating a technical decision in an interview. Start free, get feedback, and try the explanation again.
Try interview practice ↗