verify SKILL.md skillA
verify from amir20/dozzle is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amir20/dozzle/verify@git:20261105.67821dcPins git:20261105.67821dc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amir20/dozzle
- Path
.claude/skills/verify/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261105.67821dc, committed Nov 5, 2026
- Size
- 5,616 bytes
- Repository stars
- 14,814
- License
- MIT
Prove a change works before opening a PR for Dozzle. Runs the checks CI runs for what the diff touches, shows the new behaviour actually working, and has a fresh-context subagent review the diff against REVIEW.md, then writes the PR's Tests section from the real output. Use before every `gh pr create`, and whenever the user says "verify", "check it works", "is this ready for a PR" or "/verify".
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 before the PR A PR is opened only after this has passed. "It should work" or "the tests pass" is not evidence: every claim in the PR's Tests section is a command that was run and its real output. If a step can't run (no Docker, no Chrome), say so in the Tests section. Don't skip it quietly. Work on the feature branch with the change committed, so the review step sees one diff. Run `git fetch origin` first and compare against `origin/main`, which is what the CI reviewer diffs against. A worktree's local `main` is often behind, and then every step below pulls in commits that already merged: `git diff origin/main...HEAD`. ## 1. Checks for what the diff touches List the changed paths (`git diff --name-only origin/main...HEAD`) and run the matching blocks. These are the commands CI's `_tests.yml` runs, so a pass here predicts a pass there. **Go (`*.go`, `go.mod`, `protos/`, `proto/`)** ```bash make test # go test -race -count 1, after go generate go tool staticcheck ./... go tool tygo generate && git diff --exit-code assets/types/generated ! grep -n 'any /\* ' assets/types/generated/*.ts # an unmapped type; CI fails on it ``` …
Read the whole file at its exact version.
How to install
mdr add amir20/dozzle/verify@sha256:ae43cce95e76eb4aThe line at the top of this page pins the label git:20261105.67821dc, 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_ba4cnvqsv4rpvnu3)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 5, 2026.
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 (5616 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
amir20/dozzle · 14,814 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ba4cnvqsv4rpvnu3 GET https://markdownregistry.com/api/v1/resolve?ref=amir20/dozzle/verify GET https://markdownregistry.com/api/v1/blob/ae43cce95e76eb4a6594f320e0f5a45ece54992cd2e40a5fa7b713271d4217f0
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.