[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75SQ455ZWNTGQ2BPH92FSB3":3,"skill-same:01M75SQ455ZWNTGQ2BPH92FSB3":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M75SQ455ZWNTGQ2BPH92FSB3","prepare-code-freeze",null,"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, opening the required PR, and creating RC 1. Use when starting, preparing, or automating a NeMo Fabric code freeze.","NVIDIA\u002FNeMo-Fabric","NVIDIA","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1728152?v=4","01M6BXXZYTRNBXSTRXNNBB356H","NVIDIA Corporation","01M75SNZXW1HWMCP6S3FTXPVA9",75,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprepare-code-freeze\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: prepare-code-freeze\ndescription: 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, opening the required PR, and creating RC 1. Use when starting, preparing, or automating a NeMo Fabric code freeze.\nauthor: NVIDIA Corporation and Affiliates\nlicense: Apache-2.0\n---\n\n# Prepare Code Freeze\n\n## Companion Guidance\n\nUse `update-project-version` for version semantics, `maintain-ci` if the freeze\nchanges nightly or release-branch automation, `prepare-pr` before opening the\nPR, and `create-rc-tag` to create the initial release candidate.\n\n## Workflow\n\nAssume `upstream` is the NVIDIA repository remote (`NVIDIA\u002FNeMo-Fabric`) and\n`origin` is a maintainer's fork.\n\n1. Confirm the target release version from `upstream\u002Fmain:Cargo.toml`. Derive\n   the release branch as `release\u002F\u003Cmajor>.\u003Cminor>`.\n2. Prompt for `\u003Cnext-version>` if the user did not provide it. This is the\n   version that `main` moves to after the release branch is cut.\n3. Fetch the latest `main` and create the release branch from `upstream\u002Fmain`:\n\n   ```bash\n   git fetch upstream main\n   git branch release\u002F\u003Cmajor>.\u003Cminor> upstream\u002Fmain\n   git push upstream release\u002F\u003Cmajor>.\u003Cminor>\n   ```\n\n   If the remote release branch already exists, verify it points where expected\n   before continuing.\n4. Create a PR branch from latest `upstream\u002Fmain`, for example\n   `chore\u002Fversion-bump-\u003Cmajor>.\u003Cminor>`.\n5. Run `just set-version \u003Cnext-version>` to bump all release-versioned package\n   surfaces on `main`.\n6. Search documentation source for references to the old version and update\n   current-version install commands, package examples, and configuration\n   examples to `\u003Cnext-version>` where appropriate:\n\n   ```bash\n   rg -n '\u003Cold-version>' README.md docs examples adapters \\\n     --glob '!docs\u002Freference\u002Fapi\u002F**' || true\n   ```\n\n   Review matches before changing them. Leave intentional historical references\n   alone, such as release notes, changelogs, generated build output, and\n   third-party dependency attribution entries.\n7. Validate with targeted checks:\n\n   ```bash\n   just set-version \u003Cnext-version>\n   cargo check --workspace --locked\n   just build-all\n   just wheels\n   just --fmt --check\n   rg -n '\u003Cold-version>' README.md docs examples adapters \\\n     --glob '!docs\u002Freference\u002Fapi\u002F**' || true\n   git diff --check\n   ```\n\n   Any remaining documentation matches for `\u003Cold-version>` should be intentional\n   and called out in the PR description.\n8. Open a PR targeting `main` using `.github\u002Fpull_request_template.md`. The PR\n   must mention:\n   - the new release branch\n   - the nightly alpha branch config update\n   - the `just set-version \u003Cnext-version>` bump\n   - documentation old-version reference updates or intentional leftovers\n   - that release-bound PRs now target the new `release\u002F*` branch\n   - PR title should be: `chore: bump development version to \u003Cnext-version>`\n9. After the code-freeze workflow completes successfully, invoke\n   `create-rc-tag` with the target release version from step 1 and `RC_NUM=1`.\n   The version must correspond to `release\u002F\u003Cmajor>.\u003Cminor>` (for example,\n   pass `1.2.0` for `release\u002F1.2`), not `\u003Cnext-version>`.\n\n## Guardrails\n\n- Do not create an RC tag for `\u003Cnext-version>`; create RC 1 only for the target\n  release version associated with `release\u002F\u003Cmajor>.\u003Cminor>`.\n- Do not target the code-freeze PR at the release branch. It targets `main`.\n- Do not leave uncommitted user changes mixed into the code-freeze PR branch.\n","# Prepare Code Freeze\n\n## Companion Guidance\n\nUse `update-project-version` for version semantics, `maintain-ci` if the freeze\nchanges nightly or release-branch automation, `prepare-pr` before opening the\nPR, and `create-rc-tag` to create the initial release candidate.\n\n## Workflow\n\nAssume `upstream` is the NVIDIA repository remote (`NVIDIA\u002FNeMo-Fabric`) and\n`origin` is a maintainer's fork.\n\n1. Confirm the target release version from `upstream\u002Fmain:Cargo.toml`. Derive\n   the release branch as `release\u002F\u003Cmajor>.\u003Cminor>`.\n2. Prompt for `\u003Cnext-version>` if the user did not provide it. This is the\n   version that `main` moves to after the release branch is cut.\n3. Fetch the latest `main` and create the release branch from `upstream\u002Fmain`:\n\n   ```bash\n   git fetch upstream main\n   git branch release\u002F\u003Cmajor>.\u003Cminor> upstream\u002Fmain\n   git push upstream release\u002F\u003Cmajor>.\u003Cminor>\n   ```\n\n   If the remote release branch already exists, verify it points where expected\n   before continuing.\n4. Create a PR branch from latest `upstream\u002Fmain`, for example\n   `chore\u002Fversion-bump-\u003Cmajor>.\u003Cminor>`.\n5. Run `just set-version \u003Cnext-version>` to bump all release-versioned package\n   surfaces on `main`.\n6. Search documentation source for references to the old version and update\n   current-version install commands, package examples, and configuration\n   examples to `\u003Cnext-version>` where appropriate:\n\n   ```bash\n   rg -n '\u003Cold-version>' README.md docs examples adapters \\\n     --glob '!docs\u002Freference\u002Fapi\u002F**' || true\n   ```\n\n   Review matches before changing them. Leave intentional historical references\n   alone, such as release notes, changelogs, generated build output, and\n   third-party dependency attribution entries.\n7. Validate with targeted checks:\n\n   ```bash\n   just set-version \u003Cnext-version>\n   cargo check --workspace --locked\n   just build-all\n   just wheels\n   just --fmt --check\n   rg -n '\u003Cold-version>' README.md docs examples adapters \\\n     --glob '!docs\u002Freference\u002Fapi\u002F**' || true\n   git diff --check\n   ```\n\n   Any remaining documentation matches for `\u003Cold-version>` should be intentional\n   and called out in the PR description.\n8. Open a PR targeting `main` using `.github\u002Fpull_request_template.md`. The PR\n   must mention:\n   - the new release branch\n   - the nightly alpha branch config update\n   - the `just set-version \u003Cnext-version>` bump\n   - documentation old-version reference updates or intentional leftovers\n   - that release-bound PRs now target the new `release\u002F*` branch\n   - PR title should be: `chore: bump development version to \u003Cnext-version>`\n9. After the code-freeze workflow completes successfully, invoke\n   `create-rc-tag` with the target release version from step 1 and `RC_NUM=1`.\n   The version must correspond to `release\u002F\u003Cmajor>.\u003Cminor>` (for example,\n   pass `1.2.0` for `release\u002F1.2`), not `\u003Cnext-version>`.\n\n## Guardrails\n\n- Do not create an RC tag for `\u003Cnext-version>`; create RC 1 only for the target\n  release version associated with `release\u002F\u003Cmajor>.\u003Cminor>`.\n- Do not target the code-freeze PR at the release branch. It targets `main`.\n- Do not leave uncommitted user changes mixed into the code-freeze PR branch.\n",{"name":5,"author":24,"license":15,"description":7},"NVIDIA Corporation and Affiliates","main","2ffbc9d68d2383034f3b7838fc844a57c59f2b71",".agents\u002Fskills\u002Fprepare-code-freeze",47,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric","https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Ffabric","https:\u002F\u002Fgithub.com\u002FNVIDIA","https:\u002F\u002Fnvidia.com","2026-11-14 16:17:16",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add NVIDIA\u002FNeMo-Fabric --skill prepare-code-freeze",{"tool":40,"command":41},"bunx","bunx skills add NVIDIA\u002FNeMo-Fabric --skill prepare-code-freeze",{"tool":43,"command":44},"pnpm","pnpm dlx skills add NVIDIA\u002FNeMo-Fabric --skill prepare-code-freeze","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprepare-code-freeze\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M75SRD4HBPVRBVKHDNR5B8HA","default","Use this skill when asked to load the default test skill.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fdefault\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75SRBBATGBDFVYR13ASYTE3","alternate","Use this skill when asked to load the alternate test skill.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Falternate\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75SQSTED8VQDQPD6G3WZJDV","swebench-debugging","Apply a focused reproduce-fix-test workflow to SWE-Bench repository tasks.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\u002Fblob\u002Fmain\u002Fexamples\u002Fharbor\u002Fswebench\u002Fskills\u002Fswebench-debugging\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75SQRJF20D2S50TX66NSH4A","code-review","Review Python changes for correctness risks and missing test coverage.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\u002Fblob\u002Fmain\u002Fexamples\u002Fcode_review_agent\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75SQPE8FEH8JXQE41CN7EYS","validate-change","Choose and run the right NeMo Fabric validation matrix for a change instead of using one fixed test list","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvalidate-change\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75SQKT76FTB57RTPHB5ZFQ2","update-project-version","Update the NVIDIA NeMo Fabric release version across Cargo, Python, and TypeScript package metadata, internal Python dependency pins, integration metadata, and lockfiles. Use when bumping, synchronizing, or auditing NeMo Fabric package versions for a release.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNeMo-Fabric\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fupdate-project-version\u002FSKILL.md",[],[]]