vellum-pr-readiness
The vellum-pr-readiness skill validates branches before pull request creation by checking git hygiene, code scope, required documentation and migrations, Linear issue linking conventions, and test coverage. Use this skill when preparing a branch for review, deciding whether to split work across multiple PRs, or determining overall branch readiness for submission.
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/vellum-pr-readiness && cp -r /tmp/vellum-pr-readiness/.cursor/skills/vellum-pr-readiness ~/.claude/skills/vellum-pr-readinessSKILL.md
# 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. - 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 Template Use 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 Comments For non-routine changes, leave a PR comment calling out review focus and risk level. Skip this for routine low-risk changes.
Set up, authenticate, and run external coding agents (Claude Code, Codex) via the Agent Client Protocol
Shop on Amazon and Amazon Fresh through your browser
Record and analyze API surfaces of web services
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use, or to edit an app they already built here. Do NOT reach for a ui_show dynamic_page to fake an artifact — build a real persistent app here. A one-off diagram, chart, or explainer that just accompanies an answer belongs to the visualize skill (ui_show visual), not an app. NOT for complex, multi-user, or shippable products — those go to a real project folder with a coding agent (see Scope below).
Drive a specific named macOS app via raw input bypassing the Accessibility tree
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.
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready text for search, Q&A, and summarization without building a custom parsing pipeline.
Import conversation history from ChatGPT into Vellum