Claude in CI
Last lesson Claude ran on a clock. This one, it runs on an event — a pull request opens, an issue gets filed, someone mentions it by name — and Claude reacts the instant it happens.
First, the term. CI (“continuous integration”) is just the set of automated steps a team runs every time code changes — usually on every pull request (the Level 8 territory). Run the tests. Check the formatting. Now: and have Claude take a look.
Wired into CI, Claude reviews every pull request automatically — reading the diff, flagging bugs, leaving comments — without anyone remembering to ask.
How it plugs in
On GitHub, you add Claude as a step in your pipeline (Anthropic ships a ready-made GitHub Action for exactly this). Once it’s in, two things start happening:
- Open a pull request → Claude reviews it on its own and leaves comments, like a teammate who never sleeps and never gets too busy.
- Mention
@claudein a comment → “fix the failing test,” “add docs for this function” — and it does the work right there in the PR, pushing a commit back.
Under the hood it’s nothing exotic: it’s headless Claude (Lesson 11.6) running inside the pipeline, pointed at the change. Everything you learned about Claude reading code and proposing edits — now triggered by a PR instead of by you.
Why this is the one that changes teams
When review is automatic and instant, the cost of a review drops to almost nothing — so the bar for “is this worth checking?” drops with it.
A human reviewer is a scarce, interruptible resource; you save them for the changes that matter. A CI reviewer is free and tireless, so every change gets a first pass — the typo, the missed edge case, the “did you forget to handle null?” — caught before a person ever looks. Humans then spend their attention on judgment, not on catching the obvious.
The same trust rules ride along, one last time. Claude in CI proposes — comments, suggested commits — and a human still merges. You’re not handing the keys to the pipeline; you’re giving everyone a sharp-eyed first reader. Level 6 was right at the start and it’s right at the end: Claude proposes, you approve.
What’s next
That’s the last of the level’s tools — MCP, hooks, headless, the SDK, schedules, CI. They aren’t a checklist to install all at once. Pick the one that fixes a real friction this week. Drowning in copy-paste between tools? MCP. Tired of reminding Claude the same thing? A hook. PRs piling up unreviewed? CI. Add one, live with it, add the next when you hit the next wall.
And that’s every lesson in the course behind you. One page left — not a new tool, but a chance to feel how far you’ve come. Take the final exam.