How do I install the Vellum Pr Readiness skill?

Run npx skillmds@latest add vellum-ai/vellum-pr-readiness in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vellum Pr Readiness safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vellum Pr Readiness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vellum Pr Readiness free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vellum Pr Readiness?

vellum-ai (@vellum-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vellum Pr Readiness by vellum-ai — Agent Skill

Name: Vellum Pr Readiness
Author: vellum-ai

Vellum Pr Readiness

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.

vellum-ai Updated Sep 17, 2026

File contents

Vellum PR Readiness

Goal

Confirm the branch is reviewable, scoped, and verified before opening a PR. Prefer surfacing blockers over polishing summaries.

Checklist

Inspect git status and identify unrelated changes, generated artifacts, deleted files, and untracked files.
Inspect staged and unstaged diffs before recommending a commit or PR.
Check for secrets:
- Do not commit .env, credentials, tokens, private keys, or local workspace data.
- .env.example is allowed only for placeholder values.
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.
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.
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.
- Use Part of JARVIS-123 for intermediate PRs in multi-PR plans.
Check verification:
- Focused tests ran for changed behavior.
- Typecheck ran when exported contracts or cross-package types changed.
- Any skipped tests are explicitly called out.

PR Body Template

Use this compact structure unless the user asks for another format:

## Summary
- ...

## Test Plan
- ...

## Risk
- ...

Mention migrations, feature flags, rollout state, and companion PRs when relevant.

Human Attention Comments

For non-routine changes, leave a PR comment calling out review focus and risk level. Skip this for routine low-risk changes.

---name: vellum-pr-readinessdescription: 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.---# Vellum PR Readiness## GoalConfirm the branch is reviewable, scoped, and verified before opening a PR. Prefer surfacing blockers over polishing summaries.## Checklist1. 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. - Use `Part of JARVIS-123` for intermediate PRs in multi-PR plans.7. Check verification: - Focused tests ran for changed behavior. - Typecheck ran when exported contracts or cross-package types changed. - Any skipped tests are explicitly called out.## PR Body TemplateUse this compact structure unless the user asks for another format:```markdown## Summary- ...## Test Plan- ...## Risk- ...```Mention migrations, feature flags, rollout state, and companion PRs when relevant.## Human Attention CommentsFor non-routine changes, leave a PR comment calling out review focus and risk level. Skip this for routine low-risk changes.

Frequently asked questions