verify · git:20261107.3d4375e · 2026-11-07 · sha256 64138797833a5a2a
verify git:20261107.3d4375eA
Immutable. This exact content never changes and is served at /api/v1/blob/64138797833a5a2a.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rab7fur6kchbdxkh/64138797833a5a2a55c81bb802d4ffc05294aeb726b5ebaccbb074443d13aefd.json
Then /plugin install verify@markdownregistry-rab7fur6kchbdxkh in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: verify description: Run this repository's gates on the work about to be committed — the backtest suite, and the quality score for every staged `.qmd`, `.tex` or `.R` file — and stop the commit if one fails. Claude Code tells Claude to run a project skill named `verify` right before committing (not for docs-only or tests-only commits); also use it when the user says "verify", "run the gates", "check before I commit", or "is this ready to commit?". It checks and reports; it never commits, pushes or fixes anything itself. --- <!-- Generated by scripts/sync-agent-skills.py from .claude/skills/verify/SKILL.md. Do not edit: change the source and re-run the script. --> # verify This skill's instructions live in [`.claude/skills/verify/SKILL.md`](../../../.claude/skills/verify/SKILL.md). Read that file now and follow it, with the files it points to. Read [`AGENTS.md`](../../../AGENTS.md) first if you have not already. It was written for Claude Code. Running it from Codex, Antigravity or another agent: - **Arguments.** Where it says `$ARGUMENTS`, use what the user asked for. - **Claude Code agents.** Where a step hands work to an agent in `.claude/agents/` (through the `Agent` or `Task` tool), do that step where it appears in the procedure: never later, and never skip it. A step that gates what follows still gates it (`/commit` runs its verifier before it commits). Read the agent's file for what the step checks. - **Fresh context.** If the step needs a context that has not seen your work, for example a claim verifier that must never see the draft, run it in a separate session or worker that has not seen the draft, if your tool can start one, and give it only what the step says to pass. If it cannot, do the step yourself, mark every result it produced *not independently verified*, and tell the user to repeat that check in Claude Code (`/verify-claims` for citations) before relying on it. - **Claude Code settings.** `allowed-tools`, `model`, `effort`, `argument-hint` and `disable-model-invocation` in the source's frontmatter configure Claude Code. Ignore them. - **Guards.** Claude Code's guard hooks do not run for you. Follow the rules in `AGENTS.md` yourself; the git pre-commit gate and CI still apply to your commits.