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.
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/4/2026
What it changes
Passed 19 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill86%
Checks it passed that the model alone missed
Includes a `## Risk` section header.
Includes a `## Summary` section header.
Includes a `## Test Plan` section header.
and 4 more in the full report
5 fixed14 passed either way2 still failing1 broke
Pass-rate lift
+18 pp
Tokens
-28%
Agent turns
0%
Response time
-54%
Model gemini-3.6-flashMeasured 8/4/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
I am finishing issue JARVIS-456 in a single pull request. What exact clause should I put in the PR description to link and close the Linear issue?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses the Closes JARVIS-456 clause for single final pull requests.
Missed
Passed
case-05 · gemini-3.6-flash · 8/4/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md49 linessingle file
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: