SkillsAdd

nvidia/nemo-fabric · Archived

prepare-code-freeze

Prepare a NeMo Fabric code freeze by creating a release branch, deciding whether frozen-line nightly alpha tags are required, bumping main to the next version, updating current-version documentation, and opening the required PR.

Installation

$ npx skills add nvidia/nemo-fabric --skill prepare-code-freeze
View on skills.sh ↗ GitHub repository ↗

Summary

  • Prepare a NeMo Fabric code freeze by creating a release branch, deciding whether frozen-line nightly alpha tags are required, bumping main to the next version, updating current-version documentation, and opening the required PR.
  • Use when starting, preparing, or automating a NeMo Fabric code freeze.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

karpathy-guidelines Same source · more installs
nvidia/nemo-fabric

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or ref…

6 installs
python-tests Same source · more installs
nvidia/nemo-fabric

Python tests for NeMo Fabric; use this when writing tests

5 installs
contribute-api Same source · more installs
nvidia/nemo-fabric

Contribute a new NVIDIA NeMo Fabric public API surface safely, with Rust, CLI, Python, TypeScri…

5 installs
maintain-ci Same source · more installs
nvidia/nemo-fabric

Maintain and review NeMo Fabric GitHub Actions workflows with minimum permissions, pinned actio…

4 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

azure-rbac Shared topics
microsoft/azure-skills 489K installs
azure-prepare Similar name
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs
data360-prepare Similar name
forcedotcom/sf-skills

Salesforce Data Cloud Prepare phase. Use this skill when the user creates or manages Data Cloud…

3.9K installs
om-prepare-issue Similar name
open-mercato/skills

Create one well-formed tracker issue from a brief without implementing it — dedupes against exi…

38 installs
om-prepare-test-env Similar name
open-mercato/skills

Prepare a reusable, technology-agnostic environment for local tests and QA. Compiles discovery …

37 installs
sf-datacloud-prepare Similar name
jaganpro/sf-skills

Salesforce Data Cloud Prepare phase. TRIGGER when: user creates or manages Data Cloud data stre…

976 installs

Also in this package

Other skills from nvidia/nemo-fabric · top by installs.

npx skills add nvidia/nemo-fabric
karpathy-guidelines 6 python-tests 5 contribute-api 5 maintain-ci 4 validate-change 4 update-project-version 4 review-doc-style 4 maintain-packaging 4 small-fix 3 prepare-pr 3

Browse all from nvidia/nemo-fabric

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 34
License LICENSE
Default branch main
Open issues 2
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseApache-2.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,110 B
  • docs SUMMARY.md 326 B

History

  1. First recorded snapshot · 1 installs

SKILL.md

Prepare Code Freeze

Companion Guidance

Use update-project-version for version semantics, maintain-ci if the freeze changes nightly or release-branch automation, and prepare-pr before opening the PR.

Workflow

Assume upstream is the NVIDIA repository remote (NVIDIA/NeMo-Fabric) and origin is a maintainer's fork.

  1. Confirm the target release version from upstream/main:Cargo.toml. Derive

the release branch as release/<major>.<minor>.

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

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

  1. Create a PR branch from latest upstream/main, for example

docs/code-freeze-<major>.<minor>.

  1. Run just set-version <next-version> to bump all release-versioned package

surfaces on main.

  1. 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 examples adapters \ --glob '!docs/reference/api/**' || 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.

  1. Validate with targeted checks:

``bash just set-version <next-version> cargo check --workspace --locked just build-all just wheels just --fmt --check rg -n '<old-version>' README.md docs examples adapters \ --glob '!docs/reference/api/**' || true git diff --check ``

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

  1. Open a PR targeting main using .github/pullrequesttemplate.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 release-bound PRs now target the new release/* branch

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.