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.

Aller à l'installation

Dépôt: vellum-ai/vellum-assistant
Dernière activité de la source: 21 mai 2026 à 12:48
Langue détectée de SKILL.md: anglais
Étoiles: 1 091
Forks: 160

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

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

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

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

Tout voir dans ce dépôt

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.