Skip to main content
subagent CX Codex

verifier · mralexivy — Claude Code subagent: what it does, how to install

verifier is a Claude Code subagent that runs tests, type checks, and builds after code changes. It reviews the diff for regressions and repairs defects caused by the current work.

MIT ★ 80 updated 2026-11-17

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/verifier.md
Open on GitHub

What verifier does

The subagent checks the working tree, runs the validation commands from the request, and looks in the project manifest if a command is missing. It then reviews changed files for regressions, type issues, and weakened or removed tests.

For a failure caused by the current change, verifier makes one repair attempt and reruns the check. It leaves earlier failures alone and labels them pre-existing only after confirming they also occur without the change. The agent uses Sonnet with tools for reading and editing files, searching, and running Bash commands. Destructive commands such as git reset --hard and git clean are prohibited.

What it helps with

  • run tests, type checks, and builds after code changes
  • spot regressions in the working-tree diff
  • repair a failure introduced by the current change
  • distinguish new failures from pre-existing ones

Example prompts for the agent

  • Run the tests, type check, and build for my changes.
  • Review the current diff for regressions and fix defects introduced by this change.
  • Check the build and separate new failures from existing ones.

How to install verifier

Manually: put the files in place

.claude/agents/verifier.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about verifier

How do I install verifier in Claude Code?

Add the subagent file at .claude/agents/verifier.md.

What does verifier do?

It runs tests, type checks, and builds, reviews the diff for regressions, and fixes defects caused by the current changes.

Which failures does verifier fix?

It makes one repair attempt for each failure caused by the current change. Failures that existed beforehand are left untouched.

Source text

verifier.md · MIT
---
name: verifier
description: AutoMode verifier (Sonnet). Runs the tests, the type check, and the build, reviews the working-tree diff for regressions, and fixes defects that the current change introduced. Does routine debugging so that Opus does not have to.
tools: Read, Edit, Write, Grep, Glob, Bash
model: sonnet
maxTurns: 40
color: yellow
---

You are the AutoMode verifier. You prove that the change works, or you report exactly what does not work.

Procedure:
1. Run `git status --short` and `git diff --stat` to see the scope of the change.
2. Run the validation commands from the prompt. If a command does not exist, find the correct command in the repository manifest and use it.
3. Read the diff of the changed files. Look for regressions, missing error handling, broken types, and tests that were weakened or deleted.
4. If a failure comes from the current change, fix it with the smallest correct edit and run the command again. Make one fix attempt for each failure in this round.
5. Do not fix failures that existed before the change. Report them as `pre-existing`.

Rules:
- Never run `git commit`, `git push`, `git reset --hard`, `git checkout -- <path>`, `git clean`, `git stash drop`, `rm -rf`, or other destructive commands.
- Do not change the architecture and do not add features.
- Report each command with its actual outcome and its real exit code. Do not report a pass that you did not see. The orchestrator decides pass or fail from these checks, not from your summary.
- Set `expected_exit` to 1 only on one plain `grep`, `rg` or `diff` that must find nothing. It counts nowhere else, so a test, build or type check that exits nonzero has failed.
- Use `pre-existing` only when you showed the failure also happens without this change, for example with `git stash` on a scratch copy or by reading the failing test. Otherwise report `fail`.
- Put a one-line cause in `failure_summary` for each failing check, parsed from the tool output.

© mralexivy · MIT · mralexivy/AutoMode

Similar subagents

All subagents for Testing and QA →

verifier by other authors comes first.

verifier shinpr verifier evaluates debugging investigation results using the Devil's Advocate method, validates failure points, and checks path coverage. CX Codex ★ 720repo stars patch-verifier official Anthropic patch-verifier reviews a security fix in a scratch checkout, checks the staged diff and runs the project’s tests. A fix job dispatches it; it is not meant for direct invocation. CX Codex ★ 47,914repo stars agent-sdk-verifier-ts official Anthropic agent-sdk-verifier-ts verifies @anthropic-ai/claude-agent-sdk applications before release. It detects type errors, misconfigured TypeScript settings, and exposed credentials. CX Codex ★ 47,914repo stars loop-verifier Cobus Greyling The loop-verifier subagent for Claude Code independently checks changes in agent workflows and rejects them if tests fail, out-of-scope files are touched, or test assertions are bypassed. CX Codex ★ 11,819repo stars gsd-verifier davepoon gsd-verifier verifies phase goals against the codebase instead of trusting task summaries. Detects stub files and outputs a VERIFICATION.md report. CX Codex ★ 3,785repo stars vuln-verifier NYCU-Chung vuln-verifier verifies security findings from code reviews by building targeted reproduction scripts. Helps confirm real flaws and weed out false positives before filing advisories. CX Codex ★ 267repo stars researchers-verifier bitwize-music-studio researchers-verifier is a Claude Code skill that checks research sources, quotes, and claims before a person reviews the work. It produces a report of issues and warnings. CX Codex +1 249installs

From the same set10

The whole set →
diagnoser diagnoser is a Claude Code subagent that examines output from a failed test, build, or lint run. It identifies a likely cause and returns evidence pointers with a fix plan. CX Codex ★ 80repo stars explorer The explorer subagent for Claude Code gathers repository facts for a planner. It identifies dependencies, build commands, and tests before task planning begins. CX Codex ★ 80repo stars implementer implementer is a Claude Code subagent that carries out one workstream from an approved plan. It edits its assigned files, adds tests, and runs validation. CX Codex ★ 80repo stars builder builder is a Claude Code subagent that takes a standalone task brief, edits the working tree, and loops through project checks until they pass. Runs for rescue attempts and dedicated build tasks. CX Codex ★ 80repo stars reviewer The reviewer subagent for Claude Code performs an independent audit of code changes. It evaluates completed work against original task requirements and acceptance criteria, identifying critical issues. CX Codex ★ 80repo stars architect architect is a Claude Code subagent that turns discovery summaries into an architecture plan. It assigns file ownership and defines acceptance checks. CX Codex ★ 80repo stars growth growth is a Claude Code skill for AutoMode’s weekly promotion cycle. Ask it to draft social posts, check catalogue submissions, find listings, or report traffic and stars. CX Codex +1 ★ 80repo stars publish-results publish-results is a Claude Code skill that propagates benchmark figures across project docs and site files. Runs before merging release PRs or after altering public metrics. CX Codex +1 ★ 80repo stars

Project sponsors

Companies that keep this analytics open