Index of every page on this site: llms.txt
All skills
microsoft avatar

/nvx-fix-issue

@fef56ac
by microsoftmicrosoft/nvx857 stars
66
Run it yourself

Fix one microsoft/nvx 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.

  • 3 files
  • 16.8 KB
  • Updated 4 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/microsoft/nvx/nvx-fix-issue

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesopenvmm.md

≈718 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Fixing An Issue In OpenVMM

When the fix needs OpenVMM changes, the invocation's authority covers a branch of microsoft/openvmm, new commits on it, and a pull request against feature/microvm/dev; rewriting its pushed commits still needs the user's approval. The OpenVMM pull request lands first, by fast-forward, when the user decides, and the NVX pull request must not merge before the pinned revision is on feature/microvm/dev.

Branch And Pull Request

  1. Work in openvmm/ under its instructions, on a branch from the latest feature/microvm/dev, fetched by URL, since the remotes of openvmm/ can point elsewhere: git -C openvmm fetch https://github.com/microsoft/openvmm.git feature/microvm/dev. When NVX's pin is not on that branch, as git -C openvmm merge-base --is-ancestor PIN FETCH_HEAD shows, ask the user which base to use.
  2. Push the branch by URL, without force: git -C openvmm push https://github.com/microsoft/openvmm.git HEAD:refs/heads/BRANCH. Open a Ready pull request against feature/microvm/dev titled [DO NOT REVIEW] <subject>; OpenVMM's CI skips drafts and takes hours.
  3. Pin its head on the topic branch as nvx-promote-openvmm-pin describes, with its source, vector, and CPU-profile checks and its validation: a commit that changes only the gitlink and the coordinated changes that the revision needs, and a doc: commit that maps the pin in the roadmap, among the fix's other commits rather than on a two-commit branch. Check them with python3 scripts/openvmm_pin.py check-branch --topic.

Until It Lands

  • Follow the OpenVMM pull request's CI run the way the NVX one is followed, with gh pr checks M --repo microsoft/openvmm --watch --fail-fast --interval 60, and fix the failures that the change causes under the OpenVMM instructions, with new commits pushed by URL without force.
  • Whenever a fix changes that pull request's head, move the pin and the roadmap to the new head, folding them into their commits, and rerun the validation that the pin affects.
  • Before finishing, python3 scripts/openvmm_pin.py land PIN --remote REMOTE, a dry run with a remote that resolves to microsoft/openvmm, must still find a fast-forward. When another change landed there first, ask the user before rebasing the OpenVMM pull request, then force-push it only with a lease on the head that gh pr view M --repo microsoft/openvmm --json headRefOid reports, move the pin, and repeat the validation, CI, and review.
  • In the NVX pull request, tell the maintainer to land the OpenVMM pull request first by fast-forwarding feature/microvm/dev to the exact pinned revision, since OpenVMM's merge button squashes and would leave the pin off the branch.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at fef56ac. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 7 hours ago.

Activeupdated 4 days ago
argument-hint
Issue number or URL, such as 570 or https://github.com/microsoft/nvx/issues/570
disable-model-invocation
true

README badge

README badge for microsoft/nvx/nvx-fix-issue