agentleFS
vericontextvericontext/vibeframe/.agents/skills/release/SKILL.md

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

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.
  • MicrosoftSkill

    create-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

  • GrinvSkill

    changelog-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

  • GrinvSkill

    docs-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 AzureSkill

    component-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 AzureSkill

    documentation-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-devSkill

    launch-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

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
  1. Very specific:

    Use this skill when the user asks Codex to cut a VibeFrame release.

    line 8
  2. Distinctive:

    Check what the release will cover before starting:

    line 20
  3. Very specific:

    When unsure, use patch.

    line 44
  4. Distinctive:

    Read the current root version:

    line 48
  5. Distinctive:

    Read the exact new version:

    line 60
  6. Distinctive:

    Verify all package versions match:

    line 75
  7. Distinctive:

    Run the shared push gate:

    line 100
  8. Very specific:

    Commit. For a patch bump, a plain message:

    line 112
  9. Distinctive:

    Do not create a local tag.

    line 125
  10. Very specific:

    If publishing is forgotten, the daily Release drift check workflow opens an issue comparing main, the latest tag, and the published npm …

    line 150

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.sh

That 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 ordinary feat: / 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

  1. Read the current root version:

    jq -r '.version' package.json
  2. Bump the root package:

    npm version <patch|minor|major> --no-git-tag-version
  3. Read the exact new version:

    NEW_VERSION=$(jq -r '.version' package.json)
  4. Set every workspace package to that exact version. Do not use pnpm -r exec npm version for 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)
    done
  5. Verify all package versions match:

    for f in package.json packages/*/package.json apps/*/package.json; do
      jq -r '.version' "$f"
    done | sort -u

    The output must contain exactly one version.

  6. Build, regenerate references, lint, and test:

    pnpm build
    pnpm gen:reference
    pnpm lint
    pnpm -F @vibeframe/cli exec vitest run --bail 1
  7. Generate the changelog for the new version:

    git-cliff --tag v$NEW_VERSION -o CHANGELOG.md
  8. Run the shared push gate:

    bash scripts/pre-push-validate.sh
  9. Stage the release files:

    git add package.json packages/*/package.json apps/*/package.json CHANGELOG.md docs/cli-reference.md
  10. Commit. For a patch bump, 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.

  1. The version commit reaches main via a PR, never a direct push (even though main allows admin bypass). Put it on a chore/release-$NEW_VERSION branch, 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
  1. Tagging is automatic. Once the version commit lands on main and CI passes, the Create release tag workflow creates vX.Y.Z on its own. Before tagging it re-runs scripts/release-status.sh and refuses if feat: / fix: commits landed after the bump, or if CHANGELOG.md has no ## [X.Y.Z] entry. Do not create the tag by hand.
  2. Publishing stays manual. Run the Publish to npm workflow 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-created git push origin vX.Y.Z does trigger publish.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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.