The Five Minute Course
Learn Greptile in five minutes.
Greptile reads every pull request against your whole codebase and comments like a reviewer who has read all of it. Code written by one model and reviewed by a different one comes out better. Your five minutes go to reading its comments critically and closing the loop.
Plate I The lesson, live
Open full screen ↗I. The idea
A reviewer that has read the whole repo
Most review tools look at the diff. Greptile indexes the entire codebase, so it can say that a change breaks a caller three directories away. The skill is telling its real catches from its noise.
Context beyond the diff
Greptile builds a map of your repository so each comment can reference how the changed code is used elsewhere. That is where the useful catches come from.
Ranked, not just listed
Each finding comes with a confidence and a location. High-confidence, specific comments deserve action; vague ones deserve a quick read and a dismissal.
Fix, push, re-review
You or an agent address the comments, push, and Greptile reviews again. Repeat until it has nothing left to say, which is a real signal.
II. The practice
What you will do in the lesson
You answer and try things. Nobody demonstrates at you for five minutes.
- Read a Greptile review. You take a real pull request with five comments and sort them: real bug, style nit, or false alarm.
- Chase one comment to its source. You follow a comment that mentions another file and confirm whether the concern is real.
- Reply, do not just fix. You answer a comment with why you disagree and see how that becomes part of the record.
- Run a greploop. You fix the real findings, push, and read the second review to see what changed and what did not.
- Set the bar. You end by deciding which categories of comment your team should block on and which are advisory.
III. Notes
Before you start
Does Greptile replace human review?
No. It is the first pass that catches the mechanical problems so the human review can be about design and intent. Both are still needed.
Why should a different model review the code?
A model reviewing its own output shares its blind spots. Greptile's own data found that cross-model review catches more, and the lesson leans on that.
Does it need access to my private code?
Yes, it indexes the repository to review it. Check its data policy and use it on a repo you are comfortable with.
Is there a free way to try it?
There is a trial. Pricing after that is per seat or per repository; see greptile.com.
IV. Further reading
Other tools people learn next
Same format, same five minutes, still free.
Learners from these organizations are already learning on 
