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.

Ir para a instalação

Repositório: vellum-ai/vellum-assistant
Última atividade na origem: 21 de maio de 2026 às 12:48
Idioma detectado do SKILL.md: inglês
Estrelas: 1.091
Forks: 160

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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

Ver todas deste repositório

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.