Code Review Loops
Add an agentic reviewer to your pull requests, teach it the conventions only your team keeps, and close the loop so each round knows what the last one settled.
Most automated reviewers read a diff, form an opinion, and forget it by the next push. This course builds one that does better: it knows your codebase's own rules, it runs where those rules apply, and a second round can tell you what you fixed, what you explained away, and what's still open.
You'll work on a small service with a pull request that breaks three things. Two of them any competent reviewer would find. The third is a convention that exists only in that repository, and closing that gap is what the course is about.
There are two ways through. You can read each lesson on this site and step through it here, or run it hands-on in your own coding agent. The two cover the same ground, so pick whichever suits you, or do both.
To run the lessons in your agent, install the course once. Do this in a fresh
project directory (for example a new review-lab folder, because Tessl won't
initialize in your home directory):
npx tessl install tessl-academy/code-review-loops
Once the course is installed, start a lesson by asking your agent. Open your coding agent (Claude Code, Cursor, Codex, or Tessl Agent) in that directory and ask it:
"guide me through your first code review"
The installed skill picks up the request and walks you through the lesson step by step. Prefer a command? Launch it directly:
tessl launch skill --agent claude-code -i 01-your-first-code-review
Swap claude-code for cursor, codex, or tessl-agent. (Install must run
first, because tessl launch skill does not install for you.) Each lesson hands
off to the next, so your agent keeps its context as you move through the course.
This course stands on its own. Nothing here assumes you've taken Skill Foundations or Tuning Your Agent. You need the Tessl CLI, a coding agent, and a GitHub repository you can add a workflow and a secret to. Lesson 4 publishes reviews on real pull requests, so use a repository you're happy to experiment in.
One version note. Lesson 3 uses YAML review profiles, which arrived after CLI
0.96.0. Run tessl --version first, and if you installed a while ago, update
through whichever method you used to install it. See the
installation guide.
Lessons 1, 2 and 4 work on 0.96.0.
Your first code review
Run a review over a real change, read the outcome and its findings, and learn what the reviewer is actually looking at.
Writing a review lens
Turn one of your team's conventions into a lens, run it beside the defaults, and catch what a general reviewer never could.
Routing lenses by path
Put your review policy in the repository as a YAML profile, and scope each lens to the paths where its rule actually applies.
Review on every pull request
Install the caller workflow, drive a review round with a fix and a reply, and decide whether findings should block a merge.