Index of every page on this site: llms.txt
All skills
vercel avatar

/release

@250769d official
by vercelvercel/vercel-plugin340 stars
82
Run it yourself

Release vercel-plugin — run gates, bump version, generate artifacts, commit, and push. Use when asked to "release", "ship", "bump and push", or "cut a release".

  • 1 file
  • 2.2 KB
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel/vercel-plugin/release

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈43 tokens for metadata: the name and description. ≈504 when used: this file.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈170 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Release

End-to-end release workflow for vercel-plugin.

Workflow

1. Pre-flight checks

Run all gates in parallel:

bun run typecheck          # tsc --noEmit on hooks/src
bun test                   # all test files
bun run validate           # skill frontmatter + manifest integrity

Stop if any gate fails. Fix issues before proceeding.

2. Determine version bump

Read the current version from .plugin/plugin.json. Ask the user which semver component to bump if not specified:

Bump When
patch Bug fixes, test/fixture updates, docs
minor New skills, new hooks, new features
major Breaking changes to hook API or skill map

Default to patch if the user says "release" without specifying.

3. Bump version

Update the version field in .plugin/plugin.json. This is the only version source of truth.

4. Rebuild generated artifacts

bun run build:all          # hooks (tsup) + manifest

This merges upstream skills with their overlays, compiles hooks/src/*.mts → hooks/*.mjs, and resolves agent/command templates. Skill metadata is read directly from SKILL.md files.

5. Stage, commit, and push

git add -A
git commit -m "<summary>; bump to <new-version>"
git push

Commit message style: match existing convention — descriptive summary followed by ; bump to X.Y.Z (see git log for examples).

The pre-commit hook will re-run typecheck and recompile hooks automatically. If it fails, fix the issue and create a new commit (never amend).

Version source of truth

.plugin/plugin.json — the version field. There is no package.json version to sync.

Checklist (copy into your reasoning)

  • typecheck passes
  • tests pass
  • validate passes
  • .plugin/plugin.json version bumped
  • bun run build:all succeeded
  • commit includes all changes
  • pushed to main

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 250769d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month

README badge

README badge for vercel/vercel-plugin/release