release
Skill185 starsChanged todayMITView on GitHub
Bump VibeFrame versions, regenerate release artifacts, run verification, and prepare a version commit.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- releaseSkill
- sync-checkSkill
- testSkill
- vibe-pipelineSkill
- vibe-sceneSkill
- sync-checkSkill
- testSkill
- vibe-pipelineSkill
- vibe-sceneSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use this skill when the user asks Codex to cut a VibeFrame release.
- Distinctive: line 24
Check what the release will cover before starting:
- Very specific: line 48
When unsure, use patch.
- Distinctive: line 52
Read the current root version:
- Distinctive: line 64
Read the exact new version:
- Distinctive: line 79
Verify all package versions match:
- Distinctive: line 104
Run the shared push gate:
- Very specific: line 116
Commit. For a patch bump, a plain message:
- Distinctive: line 129
Do not create a local tag.
- Very specific: line 154
If publishing is forgotten, the daily Release drift check workflow opens an issue comparing main, the latest tag, and the published npm …
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- GENERATED by `pnpm agent-sync` from .agents/skills/release/SKILL.md — DO NOT EDIT. -->Release
Use this skill when the user asks Codex to cut a VibeFrame release.
The bump is one of patch, minor, or major. Default to patch when
no bump is specified or when there is any doubt.
When Bumps Happen
Once per release, not once per PR. Ordinary feat: / fix: PRs merge to
main without a version bump. This skill runs when you decide to release, and
the single bump it produces must cover every commit since the last tag -
git-cliff handles that automatically in step 7.
Check what the release will cover before starting:
bash scripts/release-status.shThat script is the single source of truth for release state. The push gate, the tag workflow, and the daily drift check all call it, so its answer is the same one CI will give.
Version Policy
VibeFrame is still in 0.x. patch is the default and by far the most
common bump. minor is rare and must be explicitly justified — the shared
push gate (scripts/pre-push-validate.sh) blocks a non-patch bump that lacks a
Release-Type: trailer (see step 10).
patch: bug fixes, docs/tooling, UX polish, internal refactors, and most ordinaryfeat:/fix:commits. Use this unless a rule below clearly applies.minor: new public CLI command namespace, new MCP tool family, public API contract additions, or a large product milestone.major: breaking changes or an intentional 1.0 milestone.
When unsure, use patch.
Steps
Read the current root version:
jq -r '.version' package.jsonBump the root package:
npm version <patch|minor|major> --no-git-tag-versionRead the exact new version:
NEW_VERSION=$(jq -r '.version' package.json)Set every workspace package to that exact version. Do not use
pnpm -r exec npm versionfor this step because recursive pnpm includes the root package.for dir in packages/cli packages/ai-providers packages/mcp-server apps/web; do (cd "$dir" && npm version "$NEW_VERSION" --no-git-tag-version) doneVerify all package versions match:
for f in package.json packages/*/package.json apps/*/package.json; do jq -r '.version' "$f" done | sort -uThe output must contain exactly one version.
Build, regenerate references, lint, and test:
pnpm build pnpm gen:reference pnpm lint pnpm -F @vibeframe/cli exec vitest run --bail 1Generate the changelog for the new version:
git-cliff --tag v$NEW_VERSION -o CHANGELOG.mdRun the shared push gate:
bash scripts/pre-push-validate.shStage the release files:
git add package.json packages/*/package.json apps/*/package.json CHANGELOG.md docs/cli-reference.md- Commit. For a
patchbump, a plain message:
git commit -m "chore: bump version to $NEW_VERSION"For a minor or major bump, the push gate requires a justification
trailer in the commit body, or it blocks the push:
git commit -m "chore: bump version to $NEW_VERSION" -m "Release-Type: minor: <why this is not a patch>"Do not create a local tag. Do not push unless the user explicitly asks.
- The version commit reaches
mainvia a PR, never a direct push (even thoughmainallows admin bypass). Put it on achore/release-$NEW_VERSIONbranch, open a PR, let CI go green, and merge:
git switch -c chore/release-$NEW_VERSION
git push -u origin chore/release-$NEW_VERSION
gh pr create --fill --base main- Tagging is automatic. Once the version commit lands on
mainand CI passes, theCreate release tagworkflow createsvX.Y.Zon its own. Before tagging it re-runsscripts/release-status.shand refuses iffeat:/fix:commits landed after the bump, or ifCHANGELOG.mdhas no## [X.Y.Z]entry. Do not create the tag by hand. Publishing stays manual. Run the
Publish to npmworkflow with the new tag.Tags pushed by a workflow cannot trigger another workflow, so the automatic tag never dispatches
publish.yml- that is what keeps the "CI never publishes" policy intact. A human-createdgit push origin vX.Y.Zdoes triggerpublish.yml, so do not push release tags manually.
If publishing is forgotten, the daily Release drift check workflow opens an
issue comparing main, the latest tag, and the published npm versions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

