[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758BCR8A21H8P4TQ0YRHTC7":3,"skill-same:01M758BCR8A21H8P4TQ0YRHTC7":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},"01M758BCR8A21H8P4TQ0YRHTC7","worktree",null,"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.","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\u002Fworktree\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: worktree\ndescription: >-\n  Create and manage isolated git worktrees for parallel build\u002Ftest\u002Flanding work\n  on the nub repo. Invoke (via the Skill tool) whenever you need a fresh\n  worktree to land a change, when you want to know what `.worktreeinclude` does\n  or how to add an entry, or when cleaning up after a merge. Encodes the\n  one-command setup (`nub scripts\u002Fnew-worktree.ts \u003Cslug>` or `node …`) that bakes\n  in the proven recipe — worktree off origin\u002Fmain (vendor\u002Faube is plain in-tree\n  files now, no submodule init), the shared CARGO_TARGET_DIR\n  (`~\u002F.cache\u002Fnub\u002Fshared-target`) that all worktrees reuse, and applying\n  `.worktreeinclude` — plus the eagerly-pull-the-shared-tree discipline and the\n  safe cleanup path. Pairs with the `dev-loop` build skill.\nmetadata:\n  internal: true\n---\n\n# Worktrees for parallel nub work\n\nSubstantive nub-repo work lands via a PR opened from an isolated git worktree; the shared working tree stays on `main` and is never branched, reset, or stashed. The whole setup is one command — don't hand-roll the `git worktree add` + target-dir recipe.\n\n## Create a worktree\n\nThe script runs under both nub (dogfood) and plain Node:\n\n```bash\nnub  scripts\u002Fnew-worktree.ts \u003Cslug>\nnode scripts\u002Fnew-worktree.ts \u003Cslug>\n```\n\nIt performs the proven recipe, in order:\n\n1. `git fetch origin` (skip with `--no-fetch`).\n2. `git worktree add ~\u002F.cache\u002Fnub\u002Fworktrees\u002F\u003Cslug> -b \u003Cslug> origin\u002Fmain` — tracked files only; the shared tree is untouched. `vendor\u002Faube` is plain in-tree files, checked out by this step with no submodule init. (Non-temp location: not auto-swept like `\u002Ftmp`, out of the repo dir, same volume so APFS clonefile stays fast.)\n3. Apply `.worktreeinclude` — copy\u002Fsymlink the listed gitignored entries in.\n4. Pre-create + print the shared `CARGO_TARGET_DIR` (`~\u002F.cache\u002Fnub\u002Fshared-target`).\n\nOptions: `--base \u003Cref>` (default `origin\u002Fmain`), `--path \u003Cdir>` (default `~\u002F.cache\u002Fnub\u002Fworktrees\u002F\u003Cslug>`), `--no-fetch`, `--help`.\n\nThen build **through the wrapper** — do not export `CARGO_TARGET_DIR` yourself; `scripts\u002Frust-build.sh` picks the right dir and CoW-seeds an isolated one when this worktree diverges a depended-on crate (see the `rust-build` skill):\n\n```bash\ncd ~\u002F.cache\u002Fnub\u002Fworktrees\u002F\u003Cslug>\nscripts\u002Frust-build.sh build -p nub-cli --profile fast\n```\n\nAll worktrees share ONE target dir (`~\u002F.cache\u002Fnub\u002Fshared-target`), so a second worktree reuses the crates.io dependency artifacts another already compiled and recompiles only the ~10 workspace crates — one target dir instead of ~30 multi-GB private ones. Tradeoff: cargo locks the target dir during a build, so two sharing worktrees serialize. Don't clean the shared dir between iterations. Build loop, profiles, and crate map: the `dev-loop` skill.\n\n## `.worktreeinclude` — bringing gitignored things in\n\n`git worktree add` checks out tracked files only, so a worktree is lean by default (no `target\u002F`, `node_modules\u002F`, `.repos\u002F`). `.worktreeinclude` at the repo root lists the gitignored things a worktree still needs; the script copies or symlinks each in.\n\nFormat — one entry per line, `#` comments and blank lines ignored:\n\n```\n[copy|symlink] \u003Cpath>      # path is relative to the repo root, both sides\n```\n\nThe verb is optional and defaults to `copy`; use `symlink` for large read-only things. Sources are read from the MAIN working tree even when you run the script from inside another worktree.\n\nThe shipped default symlinks `.repos\u002F` (read-only reference checkouts of Node, Bun, pnpm, …). **Do NOT add `target\u002F`** — the shared `CARGO_TARGET_DIR` is the build cache; an in-worktree `target\u002F` is exactly the disk bloat the shared dir avoids.\n\n## Eagerly pull the shared tree\n\nThe shared tree drifts behind `origin\u002Fmain` because every landing goes worktree → push → merge and nothing pulls it back. After merging any PR or pushing to origin:\n\n```bash\ngit -C \u003Cshared-tree> fetch origin && git -C \u003Cshared-tree> merge --ff-only origin\u002Fmain\n```\n\n**Never `git pull --ff-only` here.** This repo sets `pull.rebase=true`, so `pull` runs rebase's precondition check first and aborts with `cannot pull with rebase: You have unstaged changes` on ANY dirty file — and the shared tree always carries some agent's WIP, so that form fails 100% of the time. `merge --ff-only` has no clean-tree precondition; it refuses only if the incoming commits would overwrite a locally-modified file.\n\nCorollary: **do NOT commit directly in the shared tree's checkout** — a direct commit makes it diverge rather than merely fall behind, and a diverged tree cannot be fast-forwarded at all. If you take the sanctioned docs\u002Fcontrol-surface exception, sync immediately before committing and push in the same breath; never rest with an unpushed commit there. This keeps files current; loaded `.claude\u002F` hooks still need a session restart.\n\n## Clean up after a merge\n\n```bash\ngit worktree remove ~\u002F.cache\u002Fnub\u002Fworktrees\u002F\u003Cslug> --force   # leave ~\u002F.cache\u002Fnub\u002Fshared-target in place\n```\n\n`--force` discards the worktree even with build artifacts present — so push your work first; anything uncommitted is thrown away. **Do NOT delete `~\u002F.cache\u002Fnub\u002Fshared-target`** — it's the warm cache the next worktree builds against.\n\n**Remove ONLY the EXACT worktree path you own — never hunt for one by HEAD SHA.** If the stated path does not exist, STOP and report \"nothing to clean.\" Sibling worktrees routinely share a HEAD (two branches cut from the same base, a stacked branch off another's head), so SHA-matching deletes a different agent's active worktree and `--force`-discards its uncommitted WIP. A dispatch prompt with a cleanup step must name the exact path and add: \"remove only this path; if absent, report and stop — never match by SHA.\"\n\nThere is also an older bash helper, `scripts\u002Fworktree.sh` (worktrees under `.worktrees\u002F`, branched off LOCAL main, with `rm`\u002F`list`\u002F`reap` subcommands and uncommitted\u002Funpushed-work safety checks). `new-worktree.ts` is the preferred entry for landing work; reach for `worktree.sh reap` to prune stale dead-session worktrees.\n","# Worktrees for parallel nub work\n\nSubstantive nub-repo work lands via a PR opened from an isolated git worktree; the shared working tree stays on `main` and is never branched, reset, or stashed. The whole setup is one command — don't hand-roll the `git worktree add` + target-dir recipe.\n\n## Create a worktree\n\nThe script runs under both nub (dogfood) and plain Node:\n\n```bash\nnub  scripts\u002Fnew-worktree.ts \u003Cslug>\nnode scripts\u002Fnew-worktree.ts \u003Cslug>\n```\n\nIt performs the proven recipe, in order:\n\n1. `git fetch origin` (skip with `--no-fetch`).\n2. `git worktree add ~\u002F.cache\u002Fnub\u002Fworktrees\u002F\u003Cslug> -b \u003Cslug> origin\u002Fmain` — tracked files only; the shared tree is untouched. `vendor\u002Faube` is plain in-tree files, checked out by this step with no submodule init. (Non-temp location: not auto-swept like `\u002Ftmp`, out of the repo dir, same volume so APFS clonefile stays fast.)\n3. Apply `.worktreeinclude` — copy\u002Fsymlink the listed gitignored entries in.\n4. Pre-create + print the shared `CARGO_TARGET_DIR` (`~\u002F.cache\u002Fnub\u002Fshared-target`).\n\nOptions: `--base \u003Cref>` (default `origin\u002Fmain`), `--path \u003Cdir>` (default `~\u002F.cache\u002Fnub\u002Fworktrees\u002F\u003Cslug>`), `--no-fetch`, `--help`.\n\nThen build **through the wrapper** — do not export `CARGO_TARGET_DIR` yourself; `scripts\u002Frust-build.sh` picks the right dir and CoW-seeds an isolated one when this worktree diverges a depended-on crate (see the `rust-build` skill):\n\n```bash\ncd ~\u002F.cache\u002Fnub\u002Fworktrees\u002F\u003Cslug>\nscripts\u002Frust-build.sh build -p nub-cli --profile fast\n```\n\nAll worktrees share ONE target dir (`~\u002F.cache\u002Fnub\u002Fshared-target`), so a second worktree reuses the crates.io dependency artifacts another already compiled and recompiles only the ~10 workspace crates — one target dir instead of ~30 multi-GB private ones. Tradeoff: cargo locks the target dir during a build, so two sharing worktrees serialize. Don't clean the shared dir between iterations. Build loop, profiles, and crate map: the `dev-loop` skill.\n\n## `.worktreeinclude` — bringing gitignored things in\n\n`git worktree add` checks out tracked files only, so a worktree is lean by default (no `target\u002F`, `node_modules\u002F`, `.repos\u002F`). `.worktreeinclude` at the repo root lists the gitignored things a worktree still needs; the script copies or symlinks each in.\n\nFormat — one entry per line, `#` comments and blank lines ignored:\n\n```\n[copy|symlink] \u003Cpath>      # path is relative to the repo root, both sides\n```\n\nThe verb is optional and defaults to `copy`; use `symlink` for large read-only things. Sources are read from the MAIN working tree even when you run the script from inside another worktree.\n\nThe shipped default symlinks `.repos\u002F` (read-only reference checkouts of Node, Bun, pnpm, …). **Do NOT add `target\u002F`** — the shared `CARGO_TARGET_DIR` is the build cache; an in-worktree `target\u002F` is exactly the disk bloat the shared dir avoids.\n\n## Eagerly pull the shared tree\n\nThe shared tree drifts behind `origin\u002Fmain` because every landing goes worktree → push → merge and nothing pulls it back. After merging any PR or pushing to origin:\n\n```bash\ngit -C \u003Cshared-tree> fetch origin && git -C \u003Cshared-tree> merge --ff-only origin\u002Fmain\n```\n\n**Never `git pull --ff-only` here.** This repo sets `pull.rebase=true`, so `pull` runs rebase's precondition check first and aborts with `cannot pull with rebase: You have unstaged changes` on ANY dirty file — and the shared tree always carries some agent's WIP, so that form fails 100% of the time. `merge --ff-only` has no clean-tree precondition; it refuses only if the incoming commits would overwrite a locally-modified file.\n\nCorollary: **do NOT commit directly in the shared tree's checkout** — a direct commit makes it diverge rather than merely fall behind, and a diverged tree cannot be fast-forwarded at all. If you take the sanctioned docs\u002Fcontrol-surface exception, sync immediately before committing and push in the same breath; never rest with an unpushed commit there. This keeps files current; loaded `.claude\u002F` hooks still need a session restart.\n\n## Clean up after a merge\n\n```bash\ngit worktree remove ~\u002F.cache\u002Fnub\u002Fworktrees\u002F\u003Cslug> --force   # leave ~\u002F.cache\u002Fnub\u002Fshared-target in place\n```\n\n`--force` discards the worktree even with build artifacts present — so push your work first; anything uncommitted is thrown away. **Do NOT delete `~\u002F.cache\u002Fnub\u002Fshared-target`** — it's the warm cache the next worktree builds against.\n\n**Remove ONLY the EXACT worktree path you own — never hunt for one by HEAD SHA.** If the stated path does not exist, STOP and report \"nothing to clean.\" Sibling worktrees routinely share a HEAD (two branches cut from the same base, a stacked branch off another's head), so SHA-matching deletes a different agent's active worktree and `--force`-discards its uncommitted WIP. A dispatch prompt with a cleanup step must name the exact path and add: \"remove only this path; if absent, report and stop — never match by SHA.\"\n\nThere is also an older bash helper, `scripts\u002Fworktree.sh` (worktrees under `.worktrees\u002F`, branched off LOCAL main, with `rm`\u002F`list`\u002F`reap` subcommands and uncommitted\u002Funpushed-work safety checks). `new-worktree.ts` is the preferred entry for landing work; reach for `worktree.sh reap` to prune stale dead-session worktrees.\n",{"name":5,"metadata":24,"description":7},{"internal":25},true,"main","9b734566fd36ceed8379f67a92291bc68af60801",".claude\u002Fskills\u002Fworktree",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 worktree",{"tool":41,"command":42},"bunx","bunx skills add nubjs\u002Fnub --skill worktree",{"tool":44,"command":45},"pnpm","pnpm dlx skills add nubjs\u002Fnub --skill worktree","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworktree\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},"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":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},"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":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},"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",[],[],{"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},"01M758ARA9YKHET16KTPXNTZXR","soak","Manages the repo's supply-chain soak window (SOAK_DAYS) — checks and fixes the derived surfaces, bumps or disables the window, adds dated per-package exclusions, and bumps pinned external tools. Use when a task touches minimumReleaseAge, min-release-age, min-publish-age, external-tools.json, renovate.json, or taze cooldowns, or when investigating why a freshly published version won't install.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsoak\u002FSKILL.md",[],[]]