Verify plugin
A Claude Code plugin that verifies a change against its plan: boots your stack, runs acceptance criteria, reports evidence.
- 115 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The plugin boots the stack, runs seed scripts and repository commands and drives a browser.
- Finishing a run deletes the compose project volumes with `down -v`.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/verifyDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The plugin boots the stack, runs seed scripts and repository commands and drives a browser.
- Finishing a run deletes the compose project volumes with `down -v`.
This is third-party code. Review the repository files before installing.
What it does
Verify is a Claude Code plugin that registers the `/verify` and `/verify-setup` commands and connects Playwright MCP for browser checks. It derives acceptance criteria from the plan and the old code's behavior rather than from the diff. A second model (Codex if installed, otherwise a fresh Claude session) looks for checks that broken code would still pass. A human approves the criteria, and only after the word `go` does Verify boot the whole stack, seed data, run every criterion and tear the environment down. Each verdict in the report lists the commands and their output. A Not checked section always prints. Working files live in `.verify/`.
Who it is for. Developers who want to see that a change really works after an agent finishes, before opening a pull request.
Good fit when
- An agent wrote a feature, tests are green, but you doubt it works.
- A change touches the API, the database and the UI together and needs an end-to-end run.
- The repository has a compose file and the check should run on an isolated stack.
- The team wants an evidence report for review.
Not a fit when
- There is no change plan: Verify stops and asks for one.
- The stack cannot run locally, for example because of ties to production services.
- You need a quick check of one function, where a unit test is enough.
Example request
Run /verify for this branch against the plan in docs/plans and show the criteria before running.Limitations
Node.js must be on PATH. Verify boots a local stack: with a compose file each run gets its own project and is torn down with `down -v` including volumes, and without one it needs a start command and a health URL. It does not check a repository without a plan. The plugin is for Claude Code only and runs locally before a pull request. The first run in a repository starts with `/verify-setup`, which asks questions and writes `.verify/setup.json`. The last commit was in October 2026.
How to disable. Remove the plugin with `/plugin` and delete the `.verify/` directory in the repository. Remove the `.verify` line from `.gitignore` by hand.
FAQ
How do I install Verify in Claude Code?
With two commands: `/plugin marketplace add opslane/verify` and `/plugin install opslane-verify`. Node.js must be on PATH.
Where do the acceptance criteria come from?
From the change plan and the code behavior before the change. Verify reads the diff once and turns gaps into questions for you.
What does the report show?
Four values: how many verdicts are proven, code behavior, whether the check could run and coverage of changed files. A Not checked section always prints.
What is needed for the first run?
Run `/verify-setup`. It looks for a compose file, seed scripts and env files, asks questions and writes `.verify/setup.json`. It never asks for or stores secrets.
Where do the run results go?
To `.verify/runs/<timestamp>/` inside the repository. The directory is added to `.gitignore`.
Discussion
No questions or reviews yet.
Related
Pluginsshow-your-work
claude-show-your-work
A plugin that shows images and video in the Claude Code terminal, records Playwright checks and compares before and after
A skill that tests your agent's code in a real browser: reads your changes, builds a test plan and runs it through Playwright with your own cookies
A Claude Code hooks plugin that blocks code without a failing test and implementation beyond the current test
/pr-review sends a pull request through five independent reviewers, cross-checks findings and builds one report.
A Playwright and TypeScript project template with rules and 17 skills so Claude Code, Codex and Cursor write tests to a standard
Reviews the git diff and the conversation with the agent: catches bugs and gaps between your request and the agent's result. CLI, skill, GitHub Action
README in short
The idea is that agent tests confirm the agent's own understanding. Verify takes the reference from the plan and shows receipts rather than the word done.