verify SKILL.md skillA
verify from pedrohcgs/claude-code-my-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pedrohcgs/claude-code-my-workflow/verify@git:20261107.3d6acc5Pins git:20261107.3d6acc5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pedrohcgs/claude-code-my-workflow
- Path
.claude/skills/verify/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261107.3d6acc5, committed Nov 7, 2026
- First version recorded
- Nov 7, 2026
- Size
- 2,958 bytes
- Repository stars
- 1,718
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /verify — the gates, before a commit Since Claude Code 2.1.286, Claude is *told* to run a project skill named `verify` right before it commits, except for docs-only and tests-only commits. This one runs the same gates `/commit` runs. It is a reminder, not enforcement: Claude can skip it, and an exempt commit never triggers it, even one that changes a `.qmd` or `.tex` file. The enforcing gates are the git pre-commit hook (`./scripts/install-hooks.sh`) and `/commit`. It **does not** commit, push, stage, or edit anything. ## Steps 1. **Is the git hook already doing this?** Only when all three checks from `/commit` Step 0b hold: `git config --get core.hooksPath` prints `.githooks`; `test -x "$(git rev-parse --show-toplevel)/.githooks/pre-commit" && echo executable` prints `executable` (git skips a hook file that is missing or not executable, and still commits); and `git status --porcelain -- ':/.githooks'` prints nothing (an edited hook is itself what needs testing, and it could exit 0 without running anything). Then the pre-commit hook will run the backtest and the quality gate on this commit anyway. Say so in one line and stop, because running everything twice wastes a minute… …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xkqdqmhggoimc37g/64016f04e2ed7b55f8402ef18820acd299c7e1cc81ee32e428e855a3cf650b78.json
Then /plugin install verify@markdownregistry-xkqdqmhggoimc37g in Claude Code. It installs git:20261107.3d6acc5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add pedrohcgs/claude-code-my-workflow/verify@sha256:64016f04e2ed7b55The line at the top of this page pins the label git:20261107.3d6acc5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xkqdqmhggoimc37g)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in pedrohcgs/claude-code-my-workflow/verify since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of verify from somewhere else? Ask it: where did my verify come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, all committed on Nov 7, 2026.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261107.3d6acc5 latest | 2026-11-07 | 3d6acc5 | 2,958 B | A | view · diff |
| git:20261107.33447f3 | 2026-11-07 | 33447f3 | 2,775 B | A | view · diff |
| git:20261107.3d4375e | 2026-11-07 | 3d4375e | 2,544 B | A | view · diff |
| git:20261107.39f70a7 | 2026-11-07 | 39f70a7 | 2,296 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/verify/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2958 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pedrohcgs/claude-code-my-workflow · 1,718 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xkqdqmhggoimc37g GET https://markdownregistry.com/api/v1/resolve?ref=pedrohcgs/claude-code-my-workflow/verify GET https://markdownregistry.com/api/v1/blob/64016f04e2ed7b55f8402ef18820acd299c7e1cc81ee32e428e855a3cf650b78
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from pedrohcgs/claude-code-my-workflow
Every file in pedrohcgs/claude-code-my-workflow