[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7585PV115NA2S924STSA20V":3,"skill-same:01M7585PV115NA2S924STSA20V":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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7585PV115NA2S924STSA20V","ci-adhoc-test",null,"Run ad-hoc \u002F exploratory tests on a real OS or platform via CI when the behavior CANNOT be reproduced on the local host or in Docker — macOS Seatbelt \u002F sandbox-exec \u002F codesigning, Windows cmd.exe \u002F --script-shell shell selection \u002F .cmd resolution \u002F Authenticode, musl-vs-glibc, Linux-arm64, a specific Node floor. Invoke (via the Skill tool) whenever the user asks to \"test this on macOS\u002FWindows CI\", \"probe this across operating systems \u002F platforms\", \"run an ad-hoc cross-platform check\", or any validation that needs a real macOS or Windows runner. THE KEY FACT this skill exists to carry: a pull request is NOT required — a branch-scoped GitHub Actions workflow (workflow_dispatch + push to the branch) runs the probe with no PR open. Pairs with `ad-hoc-test` (local host probing), `dev-loop` (build), `ci-watch` (await the run), and AGENTS.md's Docker section (Linux-only; this skill covers what Docker can't).","nubjs\u002Fnub","nubjs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6785695?v=4","01M7583N3EYYHSNB6FJQXCDMQH","Nub","01M7583N44MVMSN8385QEF3C8V",4440,"MIT","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fci-adhoc-test\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ci-adhoc-test\ndescription: >-\n  Run ad-hoc \u002F exploratory tests on a real OS or platform via CI when the\n  behavior CANNOT be reproduced on the local host or in Docker — macOS Seatbelt\n  \u002F sandbox-exec \u002F codesigning, Windows cmd.exe \u002F --script-shell shell\n  selection \u002F .cmd resolution \u002F Authenticode, musl-vs-glibc, Linux-arm64, a\n  specific Node floor.\n  Invoke (via the Skill tool) whenever the user asks to \"test this on\n  macOS\u002FWindows CI\", \"probe this across operating systems \u002F platforms\", \"run an\n  ad-hoc cross-platform check\", or any validation that needs a real macOS or\n  Windows runner. THE KEY FACT this skill exists to carry: a pull request is NOT\n  required — a branch-scoped GitHub Actions workflow (workflow_dispatch + push\n  to the branch) runs the probe with no PR open. Pairs with `ad-hoc-test` (local\n  host probing), `dev-loop` (build), `ci-watch` (await the run), and AGENTS.md's\n  Docker section (Linux-only; this skill covers what Docker can't).\nmetadata:\n  internal: true\n---\n\n# Ad-hoc testing on a real OS\u002Fplatform via CI\n\nSome behavior is only observable on a real target platform: macOS Seatbelt \u002F `sandbox-exec` \u002F Gatekeeper \u002F codesigning, Windows `cmd.exe` \u002F `--script-shell` selection \u002F `.cmd`\u002F`.bat` resolution \u002F Authenticode \u002F SmartScreen, musl-vs-glibc detection, Linux-arm64, a pinned Node floor. Docker closes the **Linux** corners cheaply but runs Linux containers only — it is not a substitute for macOS or Windows.\n\n## The key fact: no PR is required\n\nA GitHub Actions workflow does not need an open pull request. Trigger it on the **branch**:\n\n```yaml\non:\n  push:\n    branches: [\u003Cyour-probe-branch>]  # THE trigger: runs on every push to THIS branch\n    paths:                           # only when the harness itself changes\n      - 'tests\u002F\u003Cprobe-name>\u002F**'\n      - '.github\u002Fworkflows\u002F\u003Cwf>.yml'\n  workflow_dispatch:                 # INERT until the file lands on the default branch — see below\n```\n\n- **Push to the branch → the probe runs.** Open no PR, or close one you opened.\n- **Re-run with another push:** `git commit --allow-empty -m rerun && git push`. Or re-run a finished run with `keyward --reason \"\u003Cthe task>\" -- gh run rerun \u003Crun-id>` (`gh run list --branch \u003Cbranch>` for the id).\n- **`push` is load-bearing; `workflow_dispatch` alone will NOT work for a branch-only probe.** GitHub only registers a `workflow_dispatch` workflow if the file is on the **default branch**, so `gh workflow run \u003Cwf>.yml --ref \u003Cbranch>` errors (\"no workflows found\") and it never appears in the Actions UI. Keep the entry for when the probe graduates to `main`; don't rely on it before then.\n- **Do NOT open a PR just to get CI.** A PR signals \"ready to land,\" which a prototype is not.\n- Omit any `pull_request:` trigger — it ties runs to PR state, which is what you're avoiding.\n\n## The harness shape\n\nKeep the probe self-contained under `tests\u002F\u003Cprobe-name>\u002F`, mirroring the existing ones:\n\n- A generator \u002F runner (e.g. an SBPL profile generator + a `sandbox-exec` runner; a `.cmd` resolver harness).\n- Fast unit + smoke tests asserting the enforcement and the bypass\u002Ffail-closed cases.\n- A `README.md` (what it validates, how to reproduce locally) and a `results.md` (findings, plus heavy runs reproduced on demand).\n- The branch-scoped workflow `.github\u002Fworkflows\u002F\u003Cwf>.yml`.\n\nMirror `tests\u002Fsandbox-macos-writeconfine\u002F` + `.github\u002Fworkflows\u002Fsandbox-macos-writeconfine.yml`, or its Windows counterpart `tests\u002Fsandbox-win-probes\u002F` (each on its own probe branch, not `main`).\n\n**Keep CI lean — fast, deterministic core only:** unit tests + the enforcement\u002Fbypass smoke matrix, no network, no mega-fixture. Heavy or combinatorial runs are documented in `results.md` and reproduced on demand. CI capacity is shared; a 22-minute-per-push probe job is already a lot.\n\n## Test every candidate FIX in one build-free run, not one per push\n\nWhen the probe fails and you have several plausible repairs, do not guess-and-push: each loop costs a\nfull build plus queue time. Write a job that tries **all** candidates at once against a stand-in, with\nno compile step — a `.cmd`\u002Fshell quoting question needs `cmd.exe` and a two-line stub, not the real\nbinary. Minutes instead of half an hour, and the losing candidates are results you keep.\n\nTwo rules that make the output trustworthy:\n\n- **Include the CURRENT broken form as a control.** It must fail. If it passes, the reproduction is\n  wrong and every other row is meaningless — say so in the output rather than reading the winners.\n- **A losing alternative is a result, not a job failure.** Exit non-zero only when the control passes\n  or when NO candidate works. Otherwise the job sits permanently red over a candidate you never\n  intended to ship, and readers learn to ignore it.\n\n## Run and watch\n\n- Kick a run by pushing to the branch; list with `gh run list --workflow \u003Cwf>.yml --branch \u003Cbranch>`.\n- Await a specific run with the `ci-watch` skill (`scripts\u002Fci-watch.ts`) rather than raw `gh run watch` — it waits for the run to exist, polls authoritative terminal status, fails fast, and exits 0 only on confirmed success.\n- A failure is immediately actionable — read the job log, fix the harness, push again.\n\n## Lifecycle\n\n- **The branch is the durable home of the probe** while it's exploratory. Push, run, iterate.\n- When it graduates into a permanent regression check, fold it into `main` through the normal flow (it's `tests\u002F**` + a workflow file — a content\u002FCI change routed straight to `main`). Decide its steady-state trigger then.\n- If you only needed the one-time answer, leave the branch as the record (or delete it once `results.md` captures the findings) — never open a PR to \"preserve\" a throwaway probe.\n\n## A cross-compile CHECK is not a test run\n\n`cargo check -p nub-cli --all-targets --target x86_64-pc-windows-gnu` proves the code COMPILES for Windows. It says nothing about whether the tests PASS there, and the gap is exactly where platform behavior lives: `.cmd` shims vs `#!\u002Fusr\u002Fbin\u002Fenv node`, path separators, `NODE_OPTIONS` tokenizing, `process.title`, mode bits that are no-ops.\n\nA cross-compile is a necessary pre-flight, never the evidence. If you are un-gating tests from `#[cfg(unix)]`, or writing anything whose behavior could differ by platform, run a branch probe BEFORE pushing — it needs no PR and costs one workflow run.\n\n## When to reach for this vs the alternatives\n\n- **Local host probe** (`ad-hoc-test`) — the behavior reproduces on your dev machine. Default for anything not platform-gated.\n- **Docker** (AGENTS.md) — a **Linux** corner: musl\u002Fglibc, a Node floor, a clean dependency-free environment, first-run install.\n- **This skill (CI branch probe)** — a **macOS or Windows** behavior, or a real multi-runner matrix, that neither the host nor Docker can show.\n","# Ad-hoc testing on a real OS\u002Fplatform via CI\n\nSome behavior is only observable on a real target platform: macOS Seatbelt \u002F `sandbox-exec` \u002F Gatekeeper \u002F codesigning, Windows `cmd.exe` \u002F `--script-shell` selection \u002F `.cmd`\u002F`.bat` resolution \u002F Authenticode \u002F SmartScreen, musl-vs-glibc detection, Linux-arm64, a pinned Node floor. Docker closes the **Linux** corners cheaply but runs Linux containers only — it is not a substitute for macOS or Windows.\n\n## The key fact: no PR is required\n\nA GitHub Actions workflow does not need an open pull request. Trigger it on the **branch**:\n\n```yaml\non:\n  push:\n    branches: [\u003Cyour-probe-branch>]  # THE trigger: runs on every push to THIS branch\n    paths:                           # only when the harness itself changes\n      - 'tests\u002F\u003Cprobe-name>\u002F**'\n      - '.github\u002Fworkflows\u002F\u003Cwf>.yml'\n  workflow_dispatch:                 # INERT until the file lands on the default branch — see below\n```\n\n- **Push to the branch → the probe runs.** Open no PR, or close one you opened.\n- **Re-run with another push:** `git commit --allow-empty -m rerun && git push`. Or re-run a finished run with `keyward --reason \"\u003Cthe task>\" -- gh run rerun \u003Crun-id>` (`gh run list --branch \u003Cbranch>` for the id).\n- **`push` is load-bearing; `workflow_dispatch` alone will NOT work for a branch-only probe.** GitHub only registers a `workflow_dispatch` workflow if the file is on the **default branch**, so `gh workflow run \u003Cwf>.yml --ref \u003Cbranch>` errors (\"no workflows found\") and it never appears in the Actions UI. Keep the entry for when the probe graduates to `main`; don't rely on it before then.\n- **Do NOT open a PR just to get CI.** A PR signals \"ready to land,\" which a prototype is not.\n- Omit any `pull_request:` trigger — it ties runs to PR state, which is what you're avoiding.\n\n## The harness shape\n\nKeep the probe self-contained under `tests\u002F\u003Cprobe-name>\u002F`, mirroring the existing ones:\n\n- A generator \u002F runner (e.g. an SBPL profile generator + a `sandbox-exec` runner; a `.cmd` resolver harness).\n- Fast unit + smoke tests asserting the enforcement and the bypass\u002Ffail-closed cases.\n- A `README.md` (what it validates, how to reproduce locally) and a `results.md` (findings, plus heavy runs reproduced on demand).\n- The branch-scoped workflow `.github\u002Fworkflows\u002F\u003Cwf>.yml`.\n\nMirror `tests\u002Fsandbox-macos-writeconfine\u002F` + `.github\u002Fworkflows\u002Fsandbox-macos-writeconfine.yml`, or its Windows counterpart `tests\u002Fsandbox-win-probes\u002F` (each on its own probe branch, not `main`).\n\n**Keep CI lean — fast, deterministic core only:** unit tests + the enforcement\u002Fbypass smoke matrix, no network, no mega-fixture. Heavy or combinatorial runs are documented in `results.md` and reproduced on demand. CI capacity is shared; a 22-minute-per-push probe job is already a lot.\n\n## Test every candidate FIX in one build-free run, not one per push\n\nWhen the probe fails and you have several plausible repairs, do not guess-and-push: each loop costs a\nfull build plus queue time. Write a job that tries **all** candidates at once against a stand-in, with\nno compile step — a `.cmd`\u002Fshell quoting question needs `cmd.exe` and a two-line stub, not the real\nbinary. Minutes instead of half an hour, and the losing candidates are results you keep.\n\nTwo rules that make the output trustworthy:\n\n- **Include the CURRENT broken form as a control.** It must fail. If it passes, the reproduction is\n  wrong and every other row is meaningless — say so in the output rather than reading the winners.\n- **A losing alternative is a result, not a job failure.** Exit non-zero only when the control passes\n  or when NO candidate works. Otherwise the job sits permanently red over a candidate you never\n  intended to ship, and readers learn to ignore it.\n\n## Run and watch\n\n- Kick a run by pushing to the branch; list with `gh run list --workflow \u003Cwf>.yml --branch \u003Cbranch>`.\n- Await a specific run with the `ci-watch` skill (`scripts\u002Fci-watch.ts`) rather than raw `gh run watch` — it waits for the run to exist, polls authoritative terminal status, fails fast, and exits 0 only on confirmed success.\n- A failure is immediately actionable — read the job log, fix the harness, push again.\n\n## Lifecycle\n\n- **The branch is the durable home of the probe** while it's exploratory. Push, run, iterate.\n- When it graduates into a permanent regression check, fold it into `main` through the normal flow (it's `tests\u002F**` + a workflow file — a content\u002FCI change routed straight to `main`). Decide its steady-state trigger then.\n- If you only needed the one-time answer, leave the branch as the record (or delete it once `results.md` captures the findings) — never open a PR to \"preserve\" a throwaway probe.\n\n## A cross-compile CHECK is not a test run\n\n`cargo check -p nub-cli --all-targets --target x86_64-pc-windows-gnu` proves the code COMPILES for Windows. It says nothing about whether the tests PASS there, and the gap is exactly where platform behavior lives: `.cmd` shims vs `#!\u002Fusr\u002Fbin\u002Fenv node`, path separators, `NODE_OPTIONS` tokenizing, `process.title`, mode bits that are no-ops.\n\nA cross-compile is a necessary pre-flight, never the evidence. If you are un-gating tests from `#[cfg(unix)]`, or writing anything whose behavior could differ by platform, run a branch probe BEFORE pushing — it needs no PR and costs one workflow run.\n\n## When to reach for this vs the alternatives\n\n- **Local host probe** (`ad-hoc-test`) — the behavior reproduces on your dev machine. Default for anything not platform-gated.\n- **Docker** (AGENTS.md) — a **Linux** corner: musl\u002Fglibc, a Node floor, a clean dependency-free environment, first-run install.\n- **This skill (CI branch probe)** — a **macOS or Windows** behavior, or a real multi-runner matrix, that neither the host nor Docker can show.\n",{"name":5,"metadata":24,"description":7},{"internal":25},true,"main","9b734566fd36ceed8379f67a92291bc68af60801",".claude\u002Fskills\u002Fci-adhoc-test",71,"https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub","https:\u002F\u002Fnubjs.com","https:\u002F\u002Fgithub.com\u002Fnubjs","The all-in-one Node.js toolkit","2026-11-14 14:11:35",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add nubjs\u002Fnub --skill ci-adhoc-test",{"tool":41,"command":42},"bunx","bunx skills add nubjs\u002Fnub --skill ci-adhoc-test",{"tool":44,"command":45},"pnpm","pnpm dlx skills add nubjs\u002Fnub --skill ci-adhoc-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fci-adhoc-test\u002FSKILL.md",[],[49,55,61,68,75,82],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M758BSH88RVXBG8TPCT427TY","nub","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002Fskills\u002Fnub\u002FSKILL.md",[],[],{"skillNo":56,"name":51,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M758BKPRHXS5MS27WG908PBG","This project uses nub, a single Rust CLI that runs on the project's installed Node and replaces the everyday Node toolchain. ALWAYS prefer nub over node, bun, npm, npx, pnpm, and yarn for: executing JS\u002FTS files, running package.json scripts, the npx-equivalent, installing dependencies, watch mode, and Node version management. Surfaces whenever you would otherwise reach for node\u002Fbun\u002Fnpm\u002Fnpx or a package manager.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002Fsite\u002Fpublic\u002Fskill.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M758BCR8A21H8P4TQ0YRHTC7","worktree","Create and manage isolated git worktrees for parallel build\u002Ftest\u002Flanding work on the nub repo. Invoke (via the Skill tool) whenever you need a fresh worktree to land a change, when you want to know what `.worktreeinclude` does or how to add an entry, or when cleaning up after a merge. Encodes the one-command setup (`nub scripts\u002Fnew-worktree.ts \u003Cslug>` or `node …`) that bakes in the proven recipe — worktree off origin\u002Fmain (vendor\u002Faube is plain in-tree files now, no submodule init), the shared CARGO_TARGET_DIR (`~\u002F.cache\u002Fnub\u002Fshared-target`) that all worktrees reuse, and applying `.worktreeinclude` — plus the eagerly-pull-the-shared-tree discipline and the safe cleanup path. Pairs with the `dev-loop` build skill.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworktree\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M758B9NZ1GQMD1A6B25NK0D9","windows-vm-test","Run ad-hoc Nub tests and debugging probes in the maintainer's existing local Windows 11 ARM64 QEMU\u002FHVF VM when its external disk and runbook are present. Use for interactive win32-arm64 or Windows-on-ARM x64-emulation checks; use ci-adhoc-test for true x64-native behavior or when the local VM is unavailable.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwindows-vm-test\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M758B2JHMBB6YJTGYSJR65S4","visual-review","Verify UI\u002Flayout\u002Fstyling changes are correct by computing occlusion, clipping, and alignment from the browser's resolved paint order via the chrome-devtools MCP `evaluate_script` tool — instead of eyeballing a flat screenshot. Invoke BEFORE declaring any UI, site, or styling\u002Flayout change correct. Screenshots have no depth buffer, so z-index\u002Focclusion\u002Fclip bugs are exactly where \"just look at it\" fails; the `evaluate_script` routines below turn those fuzzy visual judgments into deterministic measurements — including optical center-of-mass, which measures the glyph ink's true visual center so differently-sized labels can be aligned by more than eye.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvisual-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M758AWPM7CE440NBAYJHD44J","type-declarations","Add, audit, or update @nubjs\u002Ftypes declarations for Nub runtime APIs. Use whenever Nub adds or changes a user-visible global, built-in method, module loader type, or TC39 proposal; when TypeScript or @types\u002Fnode gains an overlapping declaration; and before every release to reconcile runtime changes since the previous tag. Covers conflict-safe global augmentation, compiler-version routing, fixture matrices, and package verification.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftype-declarations\u002FSKILL.md",[],[]]