Official agent skill

Prepare Code Freeze

by NVIDIA in NVIDIA/NeMo-Relay

Execute a requested NeMo Relay code freeze by cutting a release branch, updating nightly alpha configuration, bumping main, and preparing the required PR.

OfficialApache-2.0Auto-check passedDevelopment

Install Prepare Code Freeze

skills CLI
$ npx skills add NVIDIA/NeMo-Relay --skill prepare-code-freeze -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/NeMo-Relay prepare-code-freeze --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/NeMo-Relay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prepare-code-freeze .claude/skills/prepare-code-freeze && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prepare-code-freeze
GitHub stars
192
Token cost
~895 tokens
SKILL.md length
322 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

Execute a requested NeMo Relay code freeze by cutting a release branch, updating nightly alpha configuration, bumping main, and preparing the required PR.

  • Works in 9 steps: Confirm or infer the target release… → Prompt for if the user did not provide… → Fetch the latest main and create the… → …
  • An ordinary version bump
  • SKILL.md covers Workflow and Guardrails
  • Calls git, cargo and just

What it does

Prepare Code Freeze is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Execute a requested NeMo Relay code freeze by cutting a release branch, updating nightly alpha configuration, bumping main, and preparing the required PR. Do not use for an ordinary version bump or release-note draft.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with NVIDIA AI Platform. The repository describes itself as: Multi-language agent runtime and library for execution scope management, lifecycle events, and middleware on tool and LLM calls. The licence is Apache-2.0.

When your agent uses it

  • An ordinary version bump
  • Release-note draft

Example prompts

  • “/prepare-code-freeze”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Confirm or infer the target release version from upstream/main:Cargo.toml.
  2. Prompt for if the user did not provide it. This is the
  3. Fetch the latest main and create the release branch from upstream/main
  4. Create a PR branch from latest upstream/main, for example
  5. Update .github/nightly-alpha-branches.yaml to include the new release
  6. Run just set-version to update all project-owned
  7. Search documentation source for references to the old version and update
  8. Validate with targeted checks
  9. After explicit approval to publish, open a PR targeting main using

What it can do on your machine

Read from SKILL.md and the folder at commit 16d73b4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • cargo
    • just
    • rg
    • ruby

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prepare Code Freeze loads about 895 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 322 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~895

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/NeMo-Relay at commit 16d73b4, republished under its Apache-2.0 licence (© NVIDIA). 322 words, ~895 tokens.

Download SKILL.mdSave it as .claude/skills/prepare-code-freeze/SKILL.md (or your agent's skills folder).
name
prepare-code-freeze
description
Execute a requested NeMo Relay code freeze by cutting a release branch, updating nightly alpha configuration, bumping main, and preparing the required PR. Do not use for an ordinary version bump or release-note draft.
license
Apache-2.0

Prepare Code Freeze

Use this skill when the user asks to start, prepare, or automate a NeMo Relay code freeze.

Workflow

This workflow assumes upstream is the NVIDIA repository remote (NVIDIA/NeMo-Relay). The origin remote can be a maintainer's personal fork.

  1. Confirm or infer the target release version from upstream/main:Cargo.toml. Derive the release branch as release/<major>.<minor>.

  2. Prompt for <next-version> if the user did not provide it. This is the version that main moves to after the release branch is cut.

  3. Fetch the latest main and create the release branch from upstream/main:

    bash
    git fetch upstream main
    git branch release/<major>.<minor> upstream/main
    git push upstream release/<major>.<minor>

    If the remote release branch already exists, verify it points where expected before continuing.

  4. Create a PR branch from latest upstream/main, for example chore/version-bump-<major>.<minor>.

  5. Update .github/nightly-alpha-branches.yaml to include the new release branch.

  6. Run just set-version <next-version> to update all project-owned unified-release version surfaces on main, including Cargo, Python, Node, plugins, lockfiles, and coding-agent manifests. Regenerate the dynamic worker-plugin fixture lockfile so its path dependencies use the new workspace version:

    bash
    cargo generate-lockfile --manifest-path crates/core/tests/fixtures/worker_plugin/Cargo.toml
  7. Search documentation source for references to the old version and update current-version install commands, package examples, and configuration examples to <next-version> where appropriate:

    bash
    rg -n '<old-version>' README.md docs fern --glob '!docs/_build/**' || true

    Review matches before changing them. Leave intentional historical references alone, such as release notes, changelogs, generated build output, and third-party dependency attribution entries.

  8. Validate with targeted checks:

    bash
    ruby -e 'require "yaml"; YAML.load_file(".github/nightly-alpha-branches.yaml"); YAML.load_file(".github/workflows/nightly-alpha-tag.yaml")'
    just set-version <next-version>
    cargo generate-lockfile --manifest-path crates/core/tests/fixtures/worker_plugin/Cargo.toml
    cargo build --locked --manifest-path crates/core/tests/fixtures/worker_plugin/Cargo.toml
    rg -n '<old-version>' README.md docs fern --glob '!docs/_build/**' || true
    git diff --check

    Any remaining documentation matches for <old-version> should be intentional and called out in the PR description.

  9. After explicit approval to publish, open a PR targeting main using .github/pull_request_template.md. The PR must mention:

    • the new release branch
    • the nightly alpha branch config update
    • the just set-version <next-version> bump
    • documentation old-version reference updates or intentional leftovers
    • that subsequent release-bound PRs target the new release/* branch
Show full SKILL.md (41 more words)Show less

Guardrails

  • Do not create release tags. Code freeze only creates the branch and the main PR.
  • Do not target the code-freeze PR at the release branch. It targets main.
  • Do not leave uncommitted user changes mixed into the code-freeze PR branch.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/prepare-code-freeze of NVIDIA/NeMo-Relay.

Open the folder on GitHubat commit 16d73b4

Compare with similar skills

Prepare Code Freeze next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prepare Code Freeze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prepare Code Freeze this skillNVIDIA/NeMo-Relay192—~895Automated safety check: PassApache-2.0
Nemoclaw Maintainer Release NotesNVIDIA/NemoClaw23k—~2.1kAutomated safety check: PassApache-2.0
Aicr Reviewing Component DriftNVIDIA/aicr439—~2.8kAutomated safety check: PassApache-2.0
LLM Torch Profiler Analysissgl-project/sglang37k2 repos~6.4kAutomated safety check: PassApache-2.0
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
StarRocks Release NotesStarRocks/starrocks12k—~1.9kAutomated safety check: NotesApache-2.0

Similar skills

  • Official

    Draft a post-tag NemoClaw Announcement from the verified release range and shipped PRs.

    23k GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    A skill your agent uses when reviewing the weekly AICR component drift report — the Slack digest and drift-report.json artifact produced by Registry Drift Report (registry-drift.yaml) listing which…

    439 GitHub stars~2.8k tokensUpdated today
    DevOps & CloudAuto-check passed
  • LLM Torch Profiler Analysis

    sgl-project/sglang

    Unified LLM torch-profiler triage skill for sglang, vllm, TensorRT-LLM, and TokenSpeed.

    37k GitHub starsUsed in 2 repos~6.4k tokens
    DevelopmentAuto-check passed
  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed
  • StarRocks Release Notes

    StarRocks/starrocks

    Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.

    12k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes
  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

More from NVIDIA/NeMo-Relay

All 30 skills in this repo
  • Draft Release Notes

    NVIDIA/NeMo-Relay

    Official

    Compare NeMo Relay release refs and draft the current documentation release-notes page from verified repository evidence.

    192 GitHub stars~575 tokensUpdated today
    Auto-check passed
  • Official

    A skill your agent uses when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI…

    192 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Add Middleware

    NVIDIA/NeMo-Relay

    Official

    Add a new NeMo Relay guardrail or intercept type, registration surface, or pipeline stage.

    192 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Contribute Docs

    NVIDIA/NeMo-Relay

    Official

    Author or edit NeMo Relay documentation or examples when repository-specific MDX, public API, integration, or release-history conventions matter.

    192 GitHub stars~710 tokensUpdated today
    Auto-check passed
  • Maintain CI

    NVIDIA/NeMo-Relay

    Official

    Change or review NeMo Relay GitHub Actions workflows where permissions, pinned actions, caching, reusable workflows, or release gates require repository-specific handling.

    192 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Nemo Relay Install

    NVIDIA/NeMo-Relay

    Official

    A skill your agent uses when choosing or running NeMo Relay installation for the CLI, Python, Node.js, Rust, OpenClaw, or maintained framework integrations, or when explaining Hermes Agent's…

    192 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Prepare Code Freeze

What does Prepare Code Freeze do?

Execute a requested NeMo Relay code freeze by cutting a release branch, updating nightly alpha configuration, bumping main, and preparing the required PR. Prepare Code Freeze is an agent skill from NVIDIA/NeMo-Relay, published by the product's own GitHub organization. Execute a requested NeMo Relay code freeze by cutting a release branch, updating nightly alpha configuration, bumping main, and preparing the required PR.

When should I use Prepare Code Freeze?

Prepare Code Freeze fits situations like: an ordinary version bump; release-note draft.

How do I install Prepare Code Freeze in Claude Code?

Run `npx skills add NVIDIA/NeMo-Relay --skill prepare-code-freeze -a claude-code`. Or copy the skill folder (.agents/skills/prepare-code-freeze in NVIDIA/NeMo-Relay) into .claude/skills/prepare-code-freeze in your project. Claude Code loads it when a task matches its description.

How do I install Prepare Code Freeze in Codex?

Run `npx skills add NVIDIA/NeMo-Relay --skill prepare-code-freeze -a codex`. Or copy the skill folder (.agents/skills/prepare-code-freeze in NVIDIA/NeMo-Relay) into .agents/skills/prepare-code-freeze in your project. Codex loads it when a task matches its description.

Can I use Prepare Code Freeze in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/NeMo-Relay --skill prepare-code-freeze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prepare-code-freeze, .gemini/skills/prepare-code-freeze, .github/skills/prepare-code-freeze and .opencode/skills/prepare-code-freeze in your project.

What does Prepare Code Freeze need to run?

Going by SKILL.md and its folder, Prepare Code Freeze needs the command-line tools its instructions call (git, cargo, just, rg and ruby).

Does Prepare Code Freeze access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Prepare Code Freeze safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prepare Code Freeze use?

Prepare Code Freeze is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prepare Code Freeze use?

About 895 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prepare Code Freeze?

Skills that share tags, products or a category with Prepare Code Freeze: Nemoclaw Maintainer Release Notes (NVIDIA/NemoClaw, 23k stars), Aicr Reviewing Component Drift (NVIDIA/aicr, 439 stars), LLM Torch Profiler Analysis (sgl-project/sglang, 37k stars) and Simple English (moeru-ai/airi, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prepare Code Freeze?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/NeMo-Relay, which has 192 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 8, 2026.

Source: NVIDIA/NeMo-Relay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.