[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WF6DF1X138HP9B9CQCSRWA":3,"skill-same:01M6WF6DF1X138HP9B9CQCSRWA":85},{"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":23,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":48,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6WF6DF1X138HP9B9CQCSRWA","nvx-promote-openvmm-pin",null,"Pin a reviewed OpenVMM revision in NVX: verify its provenance and signature, commit the gitlink and the OpenVMM roadmap mapping, validate the exact pin, and land the OpenVMM pull request by fast-forward. Use for OpenVMM pin updates, clean replacement pull requests, source-equivalence checks, and mapping new chain commits in the OpenVMM upstream roadmap.","microsoft\u002Fnvx","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BJEK52F2VM8QAE8TEX086",835,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-promote-openvmm-pin\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"nvx promote openvmm pin","promote","pin","clean","new","request","source","for","updates","revision","URL","mapping","chain","origin","draft","upstream","pull requests","roadmap","ready","use","commits","provenance","pull","land","dev","pr","commit","2026-11-10 10:12:30",false,"---\nname: nvx-promote-openvmm-pin\ndescription: \"Pin a reviewed OpenVMM revision in NVX: verify its provenance and signature, commit the gitlink and the OpenVMM roadmap mapping, validate the exact pin, and land the OpenVMM pull request by fast-forward. Use for OpenVMM pin updates, clean replacement pull requests, source-equivalence checks, and mapping new chain commits in the OpenVMM upstream roadmap.\"\nargument-hint: \"\u003COpenVMM PR URL or revision> [target=origin\u002Fdev] [Draft|Ready]\"\n---\n\n# Promote An OpenVMM Pin\n\nA promotion is two signed NVX commits directly on the target: one that moves\nthe `openvmm` gitlink, with only the coordinated changes that the revision\nneeds, then one that maps the pinned commits in the\n[OpenVMM upstream roadmap](..\u002F..\u002F..\u002Fdoc\u002Fopenvmm-upstream-roadmap.md). Never\nmerge or copy OpenVMM history into NVX. Moving the whole chain onto a newer\nupstream `main` is [nvx-rebase-openvmm-chain](..\u002Fnvx-rebase-openvmm-chain\u002FSKILL.md)\ninstead. Commands use `python3`; use `python` on Windows.\n\n## 1. State And Inputs\n\n- Record both repositories before fetching or switching anything:\n  `git status --short --branch`, `git submodule status -- openvmm`, and\n  `git -C openvmm status --short --branch`. Never update, switch, reset, or\n  clean a dirty repository; use an approved worktree or ask. Follow\n  [the OpenVMM instructions](..\u002F..\u002F..\u002Fopenvmm\u002F.github\u002Fcopilot-instructions.md)\n  for OpenVMM source work.\n- Confirm the inputs: the OpenVMM pull request or exact revision; the target,\n  `origin\u002Fdev` once `origin` resolves to `microsoft\u002Fnvx`; prerequisite\n  revisions; whether it replaces an earlier pull request; and Draft or Ready,\n  recommending Draft until the local gates pass.\n- Fetch only the refs that you need. The tools stop on a shallow `openvmm\u002F`;\n  unshallow it from a remote that resolves to `microsoft\u002Fopenvmm`.\n\n## 2. Verify The Source\n\n```console\npython3 scripts\u002Fopenvmm_pin.py source REVISION --pr NUMBER\n```\n\nIt reports the full SHA, the signature, the tree, and the pull request's head,\nbase, state, review, and checks. Stop when the revision is missing, is not the\npull request's head, or lacks a prerequisite, and report an unverifiable\nsignature rather than treat it as verified. For a replacement of a reviewed\nrevision, `python3 scripts\u002Fopenvmm_pin.py equivalence OLD NEW --old-base B\n--new-base B` claims tree identity only for equal trees, and otherwise patch\nequivalence from the range diff; never infer equivalence from titles or file\nlists.\n\n## 3. The Gitlink Commit\n\n1. On a fresh branch from the refreshed target, with both repositories clean,\n   run `git -C openvmm switch --detach REVISION`, and inspect\n   `git diff --submodule=log -- openvmm`.\n2. Compare what `nvx-rs` copies from OpenVMM, which only the NVX CLI jobs check:\n\n   ```console\n   cargo test --locked --manifest-path nvx-rs\u002FCargo.toml --no-default-features --test openvmm_vectors -- --ignored\n   cargo test --locked --manifest-path nvx-rs\u002FCargo.toml --no-default-features --test openvmm_cpu_profiles -- --ignored\n   ```\n\n   Each stops at its first failure. Fix it and rerun until both pass:\n   - a vector file differs: copy it unchanged into\n     `nvx-rs\u002Ftests\u002Fvectors\u002Fopenvmm\u002F`, and record the revision in\n     [the vectors' README](..\u002F..\u002F..\u002Fnvx-rs\u002Ftests\u002Fvectors\u002FREADME.md#openvmms-vectors);\n   - an excerpt is no longer a run of whole lines of its file: copy the new\n     lines unchanged into it, and record the revision the same way;\n   - a contract version differs: change it in `nvx::contract`, with the code\n     that reads what it versions;\n   - a CPU profile was added, revised, or removed: update\n     `nvx-rs\u002Fsrc\u002Fhost\u002Fcli\u002Fcpu_generations.json` and the copy in\n     `scripts\u002Fnvx_tools\u002Ftime_abi.py`.\n3. `python3 scripts\u002Flocal_gates.py --run` runs the gates that these changes\n   select, such as `nvx-rs`'s and the runtime adapter's.\n4. Stage only the gitlink and the coordinated changes, and commit, signed,\n   when the user asked for commits or a pull request, with a subject such as\n   `openvmm: pin \u003Ctopic>`. Stop rather than commit unsigned, and never amend or\n   rewrite a published commit without authorization.\n\n## 4. The Roadmap Commit\n\n1. `python3 scripts\u002Fopenvmm_pin.py roadmap REVISION --target TARGET` checks\n   that the previous pin is an ancestor and that the chain has no merges, and\n   prints the pin's position and distance from the mapped tip, the new\n   commits' positions with ready-made table rows, the earlier chain commits\n   that change the same files, and whether the new commits apply to upstream\n   `main`. When the previous pin is not an ancestor, it says whether the pull\n   request needs a rebase onto the pin and new OpenVMM CI, or whether the\n   chain itself was rebased, which nvx-rebase-openvmm-chain handles.\n2. Edit the roadmap as [references\u002Froadmap.md](references\u002Froadmap.md)\n   describes, then check it, and the links, before committing:\n\n   ```console\n   python3 scripts\u002Fopenvmm_pin.py check-roadmap --worktree\n   python3 scripts\u002Fcheck_markdown_links.py\n   git diff --check\n   ```\n\n3. Commit it, signed, with a subject such as\n   `doc: map the \u003Ctopic> in the OpenVMM roadmap`, and a message that names the\n   new positions and the pin, says what the commits change, and gives the\n   pin's distance from the mapped tip.\n4. `python3 scripts\u002Fopenvmm_pin.py check-branch --target TARGET` requires\n   exactly these two signed commits on the target, the first changing the\n   gitlink and the coordinated paths that it lists, and the second only the\n   roadmap, which names the gitlink as its pin.\n\n## 5. Validate The Exact Pin\n\n- `python3 scripts\u002Fnvx.py verify`.\n- `python3 scripts\u002Fnvx.py check-openvmm-ci --revision REVISION` records\n  OpenVMM's own CI of the exact pin, which NVX CI requires\n  ([OpenVMM CI](..\u002F..\u002F..\u002Fdoc\u002Fci.md#openvmm-ci)) and which an OpenVMM pull\n  request gets only once it is ready for review, from a `microsoft\u002Fopenvmm`\n  branch. A pending job is still running; a failed one needs a rerun or a fix\n  in OpenVMM before the promotion can pass.\n- For OpenVMM source changes made in this task, run the nested repository's\n  package-scoped gates; for a pin of reviewed source, cite its exact-head\n  OpenVMM evidence, and never claim checks that did not run.\n- Choose runtime checks from the changed behavior:\n  [nvx-run-microvm](..\u002Fnvx-run-microvm\u002FSKILL.md) for a smoke test or a\n  failure, and [nvx-collect-benchmarks](..\u002Fnvx-collect-benchmarks\u002FSKILL.md)\n  only when the change needs performance evidence. Report backends that you\n  could not reach as left to CI.\n\n## 6. Pull Request And Landing\n\n- Right before pushing, fetch the target again; when it moved, rebuild both\n  commits on it, derive the roadmap's numbers again, and rerun the validation.\n- Fill the [pull request template](..\u002F..\u002Fpull_request_template.md) with the\n  OpenVMM pull request and exact pinned SHA, the scope and exclusions, the\n  prerequisites and their states, the equivalence evidence in its precise\n  term, the roadmap positions, the validation, the exact head submitted to\n  CI, and the landing order. Ask whether it is Draft or Ready.\n- Follow only the run of the current head, and triage failures with\n  [nvx-triage-ci-run](..\u002Fnvx-triage-ci-run\u002FSKILL.md). Its `openvmm-ci` job\n  waits up to 300 minutes for OpenVMM's CI of the pin; when a required OpenVMM\n  job failed, rerun it in OpenVMM, then rerun `openvmm-ci`.\n- The pinned revision must be on `feature\u002Fmicrovm\u002Fdev` before the NVX pull\n  request merges. `microsoft\u002Fopenvmm` only squash-merges, so land the OpenVMM\n  pull request by fast-forward, and only when the user asks:\n  `python3 scripts\u002Fopenvmm_pin.py land REVISION --remote REMOTE` prints the\n  push, and `--push` runs it, never forced. When the branch moved past the\n  pull request's base, the pull request needs a rebase, new OpenVMM CI, and a\n  new promotion.\n\n## Report\n\nReport the source pull request and revision, the signature, the prerequisites,\nthe equivalence method and result, the target commit, both commits and their\nfiles, the roadmap positions and the pin's distance from the mapped tip, the\ncomparisons of the vectors and CPU profiles, the local validation, the pull\nrequest's URL and state, the exact-head workflow run, the OpenVMM pull\nrequest's landing, and every blocked or pending gate.\n","# Promote An OpenVMM Pin\n\nA promotion is two signed NVX commits directly on the target: one that moves\nthe `openvmm` gitlink, with only the coordinated changes that the revision\nneeds, then one that maps the pinned commits in the\n[OpenVMM upstream roadmap](..\u002F..\u002F..\u002Fdoc\u002Fopenvmm-upstream-roadmap.md). Never\nmerge or copy OpenVMM history into NVX. Moving the whole chain onto a newer\nupstream `main` is [nvx-rebase-openvmm-chain](..\u002Fnvx-rebase-openvmm-chain\u002FSKILL.md)\ninstead. Commands use `python3`; use `python` on Windows.\n\n## 1. State And Inputs\n\n- Record both repositories before fetching or switching anything:\n  `git status --short --branch`, `git submodule status -- openvmm`, and\n  `git -C openvmm status --short --branch`. Never update, switch, reset, or\n  clean a dirty repository; use an approved worktree or ask. Follow\n  [the OpenVMM instructions](..\u002F..\u002F..\u002Fopenvmm\u002F.github\u002Fcopilot-instructions.md)\n  for OpenVMM source work.\n- Confirm the inputs: the OpenVMM pull request or exact revision; the target,\n  `origin\u002Fdev` once `origin` resolves to `microsoft\u002Fnvx`; prerequisite\n  revisions; whether it replaces an earlier pull request; and Draft or Ready,\n  recommending Draft until the local gates pass.\n- Fetch only the refs that you need. The tools stop on a shallow `openvmm\u002F`;\n  unshallow it from a remote that resolves to `microsoft\u002Fopenvmm`.\n\n## 2. Verify The Source\n\n```console\npython3 scripts\u002Fopenvmm_pin.py source REVISION --pr NUMBER\n```\n\nIt reports the full SHA, the signature, the tree, and the pull request's head,\nbase, state, review, and checks. Stop when the revision is missing, is not the\npull request's head, or lacks a prerequisite, and report an unverifiable\nsignature rather than treat it as verified. For a replacement of a reviewed\nrevision, `python3 scripts\u002Fopenvmm_pin.py equivalence OLD NEW --old-base B\n--new-base B` claims tree identity only for equal trees, and otherwise patch\nequivalence from the range diff; never infer equivalence from titles or file\nlists.\n\n## 3. The Gitlink Commit\n\n1. On a fresh branch from the refreshed target, with both repositories clean,\n   run `git -C openvmm switch --detach REVISION`, and inspect\n   `git diff --submodule=log -- openvmm`.\n2. Compare what `nvx-rs` copies from OpenVMM, which only the NVX CLI jobs check:\n\n   ```console\n   cargo test --locked --manifest-path nvx-rs\u002FCargo.toml --no-default-features --test openvmm_vectors -- --ignored\n   cargo test --locked --manifest-path nvx-rs\u002FCargo.toml --no-default-features --test openvmm_cpu_profiles -- --ignored\n   ```\n\n   Each stops at its first failure. Fix it and rerun until both pass:\n   - a vector file differs: copy it unchanged into\n     `nvx-rs\u002Ftests\u002Fvectors\u002Fopenvmm\u002F`, and record the revision in\n     [the vectors' README](..\u002F..\u002F..\u002Fnvx-rs\u002Ftests\u002Fvectors\u002FREADME.md#openvmms-vectors);\n   - an excerpt is no longer a run of whole lines of its file: copy the new\n     lines unchanged into it, and record the revision the same way;\n   - a contract version differs: change it in `nvx::contract`, with the code\n     that reads what it versions;\n   - a CPU profile was added, revised, or removed: update\n     `nvx-rs\u002Fsrc\u002Fhost\u002Fcli\u002Fcpu_generations.json` and the copy in\n     `scripts\u002Fnvx_tools\u002Ftime_abi.py`.\n3. `python3 scripts\u002Flocal_gates.py --run` runs the gates that these changes\n   select, such as `nvx-rs`'s and the runtime adapter's.\n4. Stage only the gitlink and the coordinated changes, and commit, signed,\n   when the user asked for commits or a pull request, with a subject such as\n   `openvmm: pin \u003Ctopic>`. Stop rather than commit unsigned, and never amend or\n   rewrite a published commit without authorization.\n\n## 4. The Roadmap Commit\n\n1. `python3 scripts\u002Fopenvmm_pin.py roadmap REVISION --target TARGET` checks\n   that the previous pin is an ancestor and that the chain has no merges, and\n   prints the pin's position and distance from the mapped tip, the new\n   commits' positions with ready-made table rows, the earlier chain commits\n   that change the same files, and whether the new commits apply to upstream\n   `main`. When the previous pin is not an ancestor, it says whether the pull\n   request needs a rebase onto the pin and new OpenVMM CI, or whether the\n   chain itself was rebased, which nvx-rebase-openvmm-chain handles.\n2. Edit the roadmap as [references\u002Froadmap.md](references\u002Froadmap.md)\n   describes, then check it, and the links, before committing:\n\n   ```console\n   python3 scripts\u002Fopenvmm_pin.py check-roadmap --worktree\n   python3 scripts\u002Fcheck_markdown_links.py\n   git diff --check\n   ```\n\n3. Commit it, signed, with a subject such as\n   `doc: map the \u003Ctopic> in the OpenVMM roadmap`, and a message that names the\n   new positions and the pin, says what the commits change, and gives the\n   pin's distance from the mapped tip.\n4. `python3 scripts\u002Fopenvmm_pin.py check-branch --target TARGET` requires\n   exactly these two signed commits on the target, the first changing the\n   gitlink and the coordinated paths that it lists, and the second only the\n   roadmap, which names the gitlink as its pin.\n\n## 5. Validate The Exact Pin\n\n- `python3 scripts\u002Fnvx.py verify`.\n- `python3 scripts\u002Fnvx.py check-openvmm-ci --revision REVISION` records\n  OpenVMM's own CI of the exact pin, which NVX CI requires\n  ([OpenVMM CI](..\u002F..\u002F..\u002Fdoc\u002Fci.md#openvmm-ci)) and which an OpenVMM pull\n  request gets only once it is ready for review, from a `microsoft\u002Fopenvmm`\n  branch. A pending job is still running; a failed one needs a rerun or a fix\n  in OpenVMM before the promotion can pass.\n- For OpenVMM source changes made in this task, run the nested repository's\n  package-scoped gates; for a pin of reviewed source, cite its exact-head\n  OpenVMM evidence, and never claim checks that did not run.\n- Choose runtime checks from the changed behavior:\n  [nvx-run-microvm](..\u002Fnvx-run-microvm\u002FSKILL.md) for a smoke test or a\n  failure, and [nvx-collect-benchmarks](..\u002Fnvx-collect-benchmarks\u002FSKILL.md)\n  only when the change needs performance evidence. Report backends that you\n  could not reach as left to CI.\n\n## 6. Pull Request And Landing\n\n- Right before pushing, fetch the target again; when it moved, rebuild both\n  commits on it, derive the roadmap's numbers again, and rerun the validation.\n- Fill the [pull request template](..\u002F..\u002Fpull_request_template.md) with the\n  OpenVMM pull request and exact pinned SHA, the scope and exclusions, the\n  prerequisites and their states, the equivalence evidence in its precise\n  term, the roadmap positions, the validation, the exact head submitted to\n  CI, and the landing order. Ask whether it is Draft or Ready.\n- Follow only the run of the current head, and triage failures with\n  [nvx-triage-ci-run](..\u002Fnvx-triage-ci-run\u002FSKILL.md). Its `openvmm-ci` job\n  waits up to 300 minutes for OpenVMM's CI of the pin; when a required OpenVMM\n  job failed, rerun it in OpenVMM, then rerun `openvmm-ci`.\n- The pinned revision must be on `feature\u002Fmicrovm\u002Fdev` before the NVX pull\n  request merges. `microsoft\u002Fopenvmm` only squash-merges, so land the OpenVMM\n  pull request by fast-forward, and only when the user asks:\n  `python3 scripts\u002Fopenvmm_pin.py land REVISION --remote REMOTE` prints the\n  push, and `--push` runs it, never forced. When the branch moved past the\n  pull request's base, the pull request needs a rebase, new OpenVMM CI, and a\n  new promotion.\n\n## Report\n\nReport the source pull request and revision, the signature, the prerequisites,\nthe equivalence method and result, the target commit, both commits and their\nfiles, the roadmap positions and the pin's distance from the mapped tip, the\ncomparisons of the vectors and CPU profiles, the local validation, the pull\nrequest's URL and state, the exact-head workflow run, the OpenVMM pull\nrequest's landing, and every blocked or pending gate.\n",{"name":5,"description":7,"argument-hint":56},"\u003COpenVMM PR URL or revision> [target=origin\u002Fdev] [Draft|Ready]","683eddaab528d71572503a8c687c124f35d98e10",".github\u002Fskills\u002Fnvx-promote-openvmm-pin",56,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 08:51:18",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add microsoft\u002Fnvx --skill nvx-promote-openvmm-pin",{"tool":71,"command":72},"bunx","bunx skills add microsoft\u002Fnvx --skill nvx-promote-openvmm-pin",{"tool":74,"command":75},"pnpm","pnpm dlx skills add microsoft\u002Fnvx --skill nvx-promote-openvmm-pin","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-promote-openvmm-pin\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Froadmap.md","REFERENCE","参考文档",2578,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-promote-openvmm-pin\u002Freferences\u002Froadmap.md",[86,110,136,153,175,194],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":51},"01M6WF70QXSEFAVRE1H17HCKKR","nvx-triage-ci-run","Triage a failed, cancelled, or hanging microsoft\u002Fnvx GitHub Actions run: classify supersession and queueing, find the first causal failure for the exact head, reproduce it on the matching platform, and fix it locally without committing. Use for workflow run URLs or IDs, red pull-request checks, runner, matrix, and artifact-handoff failures, and performance-gate or benchmark-host failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-triage-ci-run\u002FSKILL.md",[],[93,94,95,96,97,98,99,100,46,101,102,103,104,105,106,107,108,34,109,29],"triage","run","ci","nvx triage ci run","handoff","performance","workflow","benchmark","actions","github actions","ids","fix","runner","artifact","classify","host","matrix",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":51},"01M6WF6V0QC9BBS0DW6TB3JQN8","nvx-run-microvm","Boot an NVX microVM with nvx-rs on Linux\u002FKVM, Linux\u002FMSHV, or Windows\u002FWHP, exercise the guest, and debug failed boots. Use for boot smoke tests, guest shell sessions, virtio-fs mounts, networking, kernel command lines, missing boot markers, OpenVMM errors, guest hangs, and benchmark acceptance failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-run-microvm\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[94,120,121,122,123,124,125,126,127,128,129,43,130,131,132,108,133,134,135,31],"microvm","nvx run","nvx run microvm","kernel","linux","sessions","smoke tests","windows","kvm","exercise","smoke","local","tests","missing","markers","errors",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":51},"01M6WF6MVTYEFTS42E2JF5Y28G","nvx-rebase-openvmm-chain","Rebase or reorganize the OpenVMM microVM chain onto the latest upstream main as a new feature\u002Fmicrovm\u002Frelease branch, validate and publish it, pin it in NVX with a remapped roadmap, and land it. Use for microVM release rebases and reorganizations, chain commits that upstream landed, rebase conflicts and fixups, and the release landing order.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-rebase-openvmm-chain\u002FSKILL.md",[],[143,36,144,120,145,44,26,146,147,43,42,41,148,149,39,38,150,151,152,31,28],"rebase","nvx rebase openvmm chain","publish","branch","landing","conflicts","main","feature","as","with",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":51},"01M6WF66SSSZZZDPZEA9TR57SA","nvx-prepare-host","Prepare a local host or a configured SSH host for NVX work: resolve its profile, probe its KVM, MSHV, or WHP backend and checkout, check out the requested revision in a temporary worktree, and stage nvx-rs and the artifacts. Use before running, debugging, or benchmarking NVX on a host, or to diagnose a host's prerequisites.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-prepare-host\u002FSKILL.md",[],[160,108,161,162,163,164,128,165,166,167,168,169,43,170,171,131,172,173,31,174],"prepare","nvx prepare host","benchmarking","diagnose","debugging","artifacts","worktree","ssh","work","check","backend","probe","stage","checkout","running",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":51},"01M6WF60T85KGK0DDB14W1MQYZ","nvx-fix-issue","Fix one microsoft\u002Fnvx issue end to end: reproduce it on the configured hosts, commit signed fixes, open a Ready pull request against dev, and drive CI and review until only a maintainer's approval remains. Use when invoked with an NVX issue number or URL.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-fix-issue\u002FSKILL.md",[],[182,104,183,184,185,50,186,46,95,187,188,42,189,151,34,190,191,192,29,193],"fix issue","issue","nvx fix issue","review","issues","open","only","end","number","hosts","fixes","when",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":51},"01M6WF5V4D4J0MBBMTQTY7P5V2","nvx-collect-benchmarks","Collect fresh NVX benchmark results on a prepared Linux\u002FKVM, Linux\u002FMSHV, or Windows\u002FWHP host with the smoke, CI-equivalent, or canonical profile. Use for acceptance runs, performance suites, p50 collection, benchmark artifacts, and same-host performance comparisons.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-collect-benchmarks\u002FSKILL.md",[],[201,202,203,124,98,127,128,204,165,205,95,206,207,43,130,131,208,108,152,31],"collect","benchmarks","nvx collect benchmarks","nvx benchmark","acceptance","collection","results","fresh"]