vaultspec-code-review SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
vaultspec-code-review from nevenincs/vaultspec-core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nevenincs/vaultspec-core/vaultspec-code-review@git:20260927.50639bcPins git:20260927.50639bc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nevenincs/vaultspec-core
- Path
src/vaultspec_core/builtins/skills/vaultspec-code-review/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260927.50639bc, committed Sep 27, 2026
- First version recorded
- Jun 12, 2026
- Size
- 4,253 bytes
- Repository stars
- 2
- License
- MIT
Review completed planned work for safety, intent, and quality using applicable verification evidence. Use at the system's review cadence.
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
# Code review (vaultspec-code-review) Produces or extends an audit for work executed under a plan. Precondition: completed Steps to review. A diff with no plan behind it is reviewed in the reply, not here. This skill terminates within one run and never modifies the codebase; fixes go back to `vaultspec-execute`. ## Steps - Establish the reviewed Steps, diff base and target (including uncommitted changes), governing constraints, and unresolved risks. Reuse supplied grounding and verification evidence; inspect the plan, relevant ADR sections, ledger, and code to fill gaps. - When discovery yields competing supporting passages, optionally use `vaultspec-core review context OBJECTIVE --base REF --candidate path:start-end` (repeat `--candidate`; add `--head REF` for a committed target). The tool checks TypeSafe enrollment and falls back locally. Share one selection across reviewers; `--previous FILE` reuses judgments only for unchanged inputs. Read the full diff and governing decisions, expanding context where needed. Selection adds no review gate and establishes no verification result. …
Read the whole file at its exact version.
How to install
mdr add nevenincs/vaultspec-core/vaultspec-code-review@sha256:8d6edd301183bb28The line at the top of this page pins the label git:20260927.50639bc, 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_jmqgef4oom47irdv)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jun 12, 2026 and Sep 27, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.50639bc latest | 2026-09-27 | 50639bc | 4,253 B | A | view · diff |
| git:20260908.af390dd | 2026-09-08 | af390dd | 2,096 B | A | view · diff |
| git:20260905.f755314 | 2026-09-05 | f755314 | 1,644 B | A | view · diff |
| git:20260626.475d40c | 2026-06-26 | 475d40c | 2,199 B | A | view · diff |
| git:20260624.44a3d27 | 2026-06-24 | 44a3d27 | 2,205 B | A | view · diff |
| git:20260613.68b0c19 | 2026-06-13 | 68b0c19 | 2,137 B | A | view · diff |
| git:20260612.69d4b58 | 2026-06-12 | 69d4b58 | 2,177 B | A | view |
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 (4253 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
nevenincs/vaultspec-core · 2 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jmqgef4oom47irdv GET https://markdownregistry.com/api/v1/resolve?ref=nevenincs/vaultspec-core/vaultspec-code-review GET https://markdownregistry.com/api/v1/blob/8d6edd301183bb285c99f39f69886aa45cd4eb39bbd94acfe148a7289c51690c
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 nevenincs/vaultspec-core
Every file in nevenincs/vaultspec-core