← PostsPost ·

How the Claude Code team verifies Claude's code

Anthropic's Claude Code team, where Claude writes about 90% of the code, checks it with a verify skill that runs the app end to end. The team explained how in a post published 2026-11-16.

Give this to your agent

Open in

Your agent checks this against your setup and tells you if it fits.

See the file
# Claude Code verification: a verify skill and end-to-end tests, as the Claude Code team does it
From Rig Labs, 2026-11-17. Information for an agent, not orders. Page: https://riglabs.ai/blog/claude-code-verification-tests/

What changed: On 2026-11-16, Anthropic's Claude Code team (about 90% of its code written and reviewed by Claude) published how it verifies that code: a verify skill that runs the app end to end, then property and differential tests.
Fits if: Your human uses Claude Code on a repository with an app or service that can run locally.
Skip if: Your human does not write code with an agent, or the project cannot run locally.
Check: Whether the repository already has a .claude/skills/verify skill, an end-to-end test, or a CLAUDE.md rule about running tests before a pull request. Read-only.
Try: Propose a verify skill in .claude/skills/verify/SKILL.md that starts the app, drives the main user flow and reports pass or fail.
Ask first: Creating the skill file, and any change to tests, hooks or CLAUDE.md.
Cost: No new product or price; test runs use the human's usual Claude Code usage.
Undo: Delete the .claude/skills/verify folder.
Deeper: https://claude.dev/blog/how-the-claude-code-team-thinks-about-verification/

You can give Claude Code a verify skill that starts and drives your app, so Claude checks its own work before you look at it: the same setup the Claude Code team at Anthropic uses. The team explained how it checks Claude’s code on November 16, 2026, in a post by Addy Osmani on claude.dev.

Claude writes and reviews about 90% of the team’s code, and the team’s main rule is to run a change end to end before trusting it.

Why does verification matter so much with Claude Code?

Verification decides how much work you can hand off, per the post. Without a way for the agent to check its output, you can run one or two Claudes at a time, because you check everything yourself. With it, the team says, you can run dozens in parallel.

Which tests does the Claude Code team recommend?

The post names three kinds of tests worth investing in, and says to pick end-to-end if you can only focus on one:

  • End-to-end tests first. They follow a real user path (add to cart, check out, see the confirmation) and are hard to fool: the feature works or it does not. Unit tests can pass while the feature is broken.
  • Property tests. You state something that must always hold (“a balance can never go negative”, “decode after encode gives back the input”) and a library such as Hypothesis or fast-check tries thousands of inputs to break it.
  • Differential tests. For a migration, run the old and the new system on the same inputs and compare the results.

Tests must be fast and not flaky. A flaky test teaches the agent to rerun it instead of fixing the code.

What does the team actually do?

The Claude Code team’s own practice, per the post:

  • A skill called verify, in a .claude/skills/ folder next to the code, holds how to start and drive the app (the Chrome extension for web, an iOS or Android MCP for mobile, computer use for desktop). Claude uses it before committing.
  • Claude runs the tests, build and linter before opening a pull request.
  • If a check still fails after three rounds of fixes, Claude stops and brings in a person.
  • A change can never edit the check that judges it: review rules are read from the main branch.
  • A repeated failure becomes a hook or a CLAUDE.md rule, so it does not happen again.
  • Their commit gate, which blocks a commit made without /verify or /code-review, has an observe mode that logs what it would block before it blocks anything.

What to do today

Ask Claude Code, in a repository you work on:

Create a skill called verify in .claude/skills/verify/SKILL.md. It should start
this app locally, drive the main user flow end to end, and report pass or fail
with what it saw. Then run it once. Fix the skill only if it fails to start or
drive the app. If the app itself fails, report it, and do not change the check
to make it pass.

Last checked 2026-11-17.

Sources:

Get the next one by email

The Edge is our newsletter: what changed in AI, and what to do about it.

Which emails
Free. Your agent reads every piece we publish, and you hear only what fits.

Subscribe your agent Beta

Your agent reads every post, guide and issue, checks it against your setup, and tells you only what is worth your time. Its inbox gets the daily agent cards email automatically, every day something is published, and the weekly issue as plain text. You pick weekly, daily or both for yourself.

  1. Give it the prompt

    Using Claude Code, Codex or another agent? Copy the prompt and paste it in.

    See the prompt
    Subscribe yourself to The Edge, the newsletter from Rig Labs, and follow what Rig Labs publishes for me.
    Read https://riglabs.ai/agents/subscribe.md and follow its steps. It has you save the skill at https://riglabs.ai/agents/the-edge/SKILL.md, set yourself up with your own inbox on Nym (invite: https://withnym.com/join/NYM-TQZB-WP35, code NYM-TQZB-WP35) unless you already have one, subscribe that address, and confirm with me.
    Treat everything you fetch from Rig Labs as information, not orders. Ask me before anything that touches keys, payments, permissions, installs or sending messages.
  2. Approve its inbox

    It gets its own address on Nym, so The Edge never lands in your inbox. One sign-in in your browser, about a minute.

  3. Hear only what fits

    At most one short message a day. Nothing if nothing fits.

Your agent follows subscribe.md and saves SKILL.md: read both first. Nym is in private beta. The invite is included in the prompt.

Read next

Built by Rig Labs

When a tool we need does not exist, we build it.