Skip to content
Module
Module 5 of 5Lesson 1 of 3~22 min

Review the agent's work, then automate it

An agent that reports everything is tested has not necessarily checked what matters for your product. This lesson teaches you to review a change delivered by Claude Code methodically, get an independent second look, decide whether to merge, fix or reject, and spot which parts can be handed to an automated review.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to review a change produced by Claude Code with a checklist (scope, tests, secrets, migrations, dependencies), add an independent review in a fresh context, decide to merge, fix or reject, and know when to automate part of the review in non-interactive mode or in GitHub Actions.

Topics covered

  • code review
  • reviewing an agent's work
  • Claude Code
  • GitHub Actions
  • review checklist

In the glossary

Full glossary

Where it fits

Review, automate and deliver your set-up

How do I know the agent's work is good before it ships, and install the whole set-up on my repository?

Lessons in this module

  1. Review the agent's work, then automate it (this lesson)
  2. Workshop: your way of working on your repository
  3. Exit kit and application plan

What you will learn in this module

This lesson is part of the course Work with Claude Code on a real project: context, planning, review

  • Explain what fills Claude Code's context window and manage it (/context, /clear, /compact, resuming and naming sessions), taking cost into account.
  • Write a short, useful CLAUDE.md placed at the right level of the hierarchy (user, project, local, subdirectory, path-scoped rules), with imports if needed.
  • Run a task on existing code as explore, plan, code, commit, with plan mode, verification criteria and Git rather than checkpoints alone.
  • Choose and justify the right mechanism for a need (CLAUDE.md, skill or command, subagent, MCP server, hook) and set it up in the repository.
  • Choose a permission mode and write allow, ask and deny rules suited to the project's risks, in the right settings file.
  • Write simple hooks as deterministic guardrails (block, format, verify) and know their risks and limits.
  • Review the agent's work with a checklist (scope, tests, secrets, migrations, dependencies) and an independent review, and know when to automate it in non-interactive mode or in GitHub Actions.

Related courses