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/vellum-assistant
最近来源活动: 2026年5月21日 12:48
检测到的 SKILL.md 语言: 英语
星标: 1,091
分支: 160

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/vellum-ai/vellum-assistant --skill vellum-pr-readiness

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

plugin-builder

Use when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.

2026-08-18

vellum-memory-v2-migration

Perform a one-time migration from memory v1, to memory v2, which was introduced in 0.8.0.

2026-08-18

assistant-migration

Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum primitives. Handles single-source and multi-source migrations with a unified, deduplicated inventory.

2026-08-18

查看这个仓库的全部 Skills

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-readiness
description	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.