vellum-pr-readiness SKILL.md skillA
vellum-pr-readiness from vellum-ai/vellum-assistant is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vellum-ai/vellum-assistant/vellum-pr-readiness@git:20260521.b4bdd7aPins git:20260521.b4bdd7a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vellum-ai/vellum-assistant
- Path
.cursor/skills/vellum-pr-readiness/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260521.b4bdd7a, committed May 21, 2026
- Size
- 2,130 bytes
- Repository stars
- 1,467
- License
- MIT
Prepare Vellum Assistant branches for review by checking git hygiene, PR scope, tests, docs, migrations, Linear linking, and companion repo needs. Use before creating a pull request, splitting work into PRs, or asking whether a branch is ready.
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
# Vellum PR Readiness ## Goal Confirm the branch is reviewable, scoped, and verified before opening a PR. Prefer surfacing blockers over polishing summaries. ## Checklist 1. Inspect `git status` and identify unrelated changes, generated artifacts, deleted files, and untracked files. 2. Inspect staged and unstaged diffs before recommending a commit or PR. 3. Check for secrets: - Do not commit `.env`, credentials, tokens, private keys, or local workspace data. - `.env.example` is allowed only for placeholder values. 4. Check scope: - If the branch is too large, suggest splitting it into smaller, reviewable PR branches. - Separate unrelated UI, backend, migration, and infra changes when practical. 5. Check required follow-ups: - Migration needed for persisted data or workspace format changes. - Docs needed for significant architecture, service, or data-flow changes. - Companion `vellum-assistant-platform` PR needed for platform-affecting contracts or new feature flags. 6. Check Linear conventions: - Branch, commit body, and PR body should include the Linear issue ID when one exists. - Use `Closes JARVIS-123` for single final PRs. …
Read the whole file at its exact version.
How to install
mdr add vellum-ai/vellum-assistant/vellum-pr-readiness@sha256:40c0d3538537f16cThe line at the top of this page pins the label git:20260521.b4bdd7a, 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_eso3sm7v5vhld6it)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 21, 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 (2130 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
vellum-ai/vellum-assistant · 1,467 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eso3sm7v5vhld6it GET https://markdownregistry.com/api/v1/resolve?ref=vellum-ai/vellum-assistant/vellum-pr-readiness GET https://markdownregistry.com/api/v1/blob/40c0d3538537f16c1b9896abf3cd4df306434aa35961e53b1624c86f69408174
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.