[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7586AAWWMZBKMDWNQGT7ZZX":3,"skill-same:01M7586AAWWMZBKMDWNQGT7ZZX":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},"01M7586AAWWMZBKMDWNQGT7ZZX","ci-watch",null,"Watch GitHub Actions CI correctly with the gh CLI — block until a run \u002F PR check rollup is TRULY terminal, then trust the exit code. Invoke (via the Skill tool) whenever you need to wait on CI after REQUESTING a pull-request run (`gh pr edit \u003Cn> --add-label ci` — PR CI is opt-in, so a push starts nothing), after a push to main, or after a tag, and act on the result (merge-on-green, release-on-green, fail-fast on red). Encodes the premature-exit pitfall (raw `gh run watch` \u002F `gh pr checks --watch` exit 0 while the run is still QUEUED with no jobs registered, and exit non-zero on a transient API blip) and the blessed fix: `scripts\u002Fci-watch.ts`, which waits for the target to EXIST, polls authoritative terminal status, fails fast on the first failing check, and exits with a status the orchestrator can trust. Run it as a detached run_in_background task.","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-watch\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ci-watch\ndescription: >-\n  Watch GitHub Actions CI correctly with the gh CLI — block until a run \u002F PR\n  check rollup is TRULY terminal, then trust the exit code. Invoke (via the Skill\n  tool) whenever you need to wait on CI after REQUESTING a pull-request run\n  (`gh pr edit \u003Cn> --add-label ci` — PR CI is opt-in, so a push starts nothing),\n  after a push to main, or after a tag, and act on the result (merge-on-green,\n  release-on-green, fail-fast on red). Encodes the\n  premature-exit pitfall (raw `gh run watch` \u002F `gh pr checks --watch` exit 0\n  while the run is still QUEUED with no jobs registered, and exit non-zero on a\n  transient API blip) and the blessed fix: `scripts\u002Fci-watch.ts`, which waits for\n  the target to EXIST, polls authoritative terminal status, fails fast on the\n  first failing check, and exits with a status the orchestrator can trust. Run it\n  as a detached run_in_background task.\nmetadata:\n  internal: true\n---\n\n# Watching CI with the GitHub CLI\n\nWatching only reads, so it stays plain `gh`. The one write here, `gh pr edit \u003Cn> --add-label ci`, runs as `keyward --reason \"\u003Cthe task>\" -- gh pr edit …` on the maintainer's Mac.\n\n## The pitfall: raw watchers exit early\n\n`gh run watch \u003Cid> --exit-status` and `gh pr checks \u003Cpr> --watch` are not safe to arm right after a push \u002F tag \u002F PR-open:\n\n- **Premature exit while QUEUED.** With no jobs registered yet, gh sees \"nothing in progress\" and returns **exit 0** even though the run is still queued.\n- **Transient errors read as failure.** A mid-watch `HTTP 401: Bad credentials` (token refresh) or a 5xx exits non-zero, indistinguishable from a real CI failure.\n- **No native fix** — `--interval` only tunes the poll cadence.\n\n**Never trust a raw watcher's exit code alone.** Re-verify terminal status with `gh run view \u003Cid> --json status,conclusion` (done only when `status == \"completed\"`) or `gh pr view \u003Cpr> --json statusCheckRollup` (done only when every item is terminal). And always fail-fast — act on the first failing check, never wait for all checks to finish.\n\n## The blessed tool: `scripts\u002Fci-watch.ts`\n\nBlocks until the target is truly terminal, then exits with a trustworthy status. Dogfoods nub; runs under plain Node too.\n\n```bash\nnub  scripts\u002Fci-watch.ts --run \u003Crun-id> [--repo o\u002Fr] [--timeout \u003Cmin>]\nnode scripts\u002Fci-watch.ts --pr  \u003Cnumber> [--repo o\u002Fr] [--timeout \u003Cmin>]\n```\n\n- `--run \u003Crun-id>` — watch a workflow run (polls `gh run view --json status,conclusion,jobs`).\n- `--pr \u003Cnumber>` — watch a PR's check rollup (polls `gh pr view --json statusCheckRollup,…`).\n- `--repo \u003Cowner\u002Frepo>` — defaults to the current repo.\n- `--timeout \u003Cminutes>` — wall-clock cap before giving up as pending (default 45).\n- `--required \u003Cnames>` — comma-separated branch-protection check names to gate on (e.g. `--required \"CI gate\"`). Success fires the instant every required check is green; a ghost or a non-required check — pending *or* failed — never blocks, matching branch-protection semantics. Prefer it when you know the required check name.\n- `--no-progress \u003Cminutes>` — how long an unchanged incomplete set (all named checks green, only a ghost left) may sit before exiting 4 STUCK-but-safe (default 8).\n\nWhat it fixes: **waits for the target to EXIST** (not-found \u002F no-jobs-yet is \"keep polling,\" never \"done\"); polls authoritative terminal state; **fails fast** on the first FAILURE\u002FCANCELLED\u002FTIMED_OUT\u002F STARTUP_FAILURE; **never hangs on a ghost**; **tolerates transient** gh\u002FAPI errors (retried with exponential jittered backoff, 10s → cap 60s, 90s unauthenticated).\n\n### The ghost check — why a strict \"all checks terminal\" gate hangs\n\nGitHub occasionally registers a check-run that never reports a status: PENDING, nameless, forever. A watcher waiting for *every* rollup item to be terminal blocks indefinitely even though every real check is green. So a nameless \u002F never-terminating non-required check does not block a green verdict: once every named check is green and the incomplete set has been unchanged for `--no-progress` minutes, the watcher exits **4 (STUCK-but-safe)** and the caller `--admin` merges. A *named* pending check is never treated as a ghost, so a real in-flight check is never green-lit early.\n\n### Exit-code contract\n\n| code | meaning |\n| ---- | ------- |\n| 0 | completed AND all green |\n| 1 | a check\u002Fjob failed (the summary names which + the URL) |\n| 2 | required\u002Fnamed checks still NOT green after `--timeout` (genuinely stuck) |\n| 3 | usage \u002F target-unresolvable \u002F unrecoverable error |\n| 4 | STUCK-but-safe — required\u002Fnamed checks all green, but a ghost check will never terminate; safe to `--admin` merge (the caller decides) |\n\nThe final stdout line is a single self-describing summary, e.g. `CI-WATCH run 27972328590: SUCCESS (25 job(s) green)`, `CI-WATCH pr 73: FAILURE — check \"Test (ubuntu-latest, node 22.13)\" → FAILURE (https:\u002F\u002F…)`, or `CI-WATCH pr 327: STUCK — required\u002Fnamed checks GREEN (51), 1 non-terminal ghost\u002Fnon-required check(s): (unnamed); safe to --admin merge`.\n\n### NEVER pipe the watcher — a pipe discards the verdict you gate on\n\nThe exit code IS the contract, and a pipeline throws it away: in `ci-watch.ts … | tail -20`, `$?` is **tail's** status, so a **FAILED CI reads as SUCCESS**. The pipe also buffers stdout until the pipeline ends, so the log stays empty while the watcher runs.\n\n```bash\n# WRONG — $? is tail's, a red CI looks green, and no interim output\nnode scripts\u002Fci-watch.ts --pr 604 --repo nubjs\u002Fnub | tail -25; echo \"exit=$?\"\n\n# RIGHT — redirect, then gate on the watcher's OWN status\nnode scripts\u002Fci-watch.ts --pr 604 --repo nubjs\u002Fnub > \u002Ftmp\u002Fci604.log 2>&1; rc=$?\ntail -15 \u002Ftmp\u002Fci604.log; echo \"exit=$rc\"\n```\n\n`main()` warns on stderr when it detects a piped stdout (fd 1 is a FIFO for `| cmd`, not for `> file`), but redirect by default rather than relying on the warning. Bash `${PIPESTATUS[0]}` \u002F zsh `${pipestatus[1]}` recover the real status if a pipe is unavoidable.\n\n**Cross-check the rollup regardless of what the watcher says.** Read `gh pr view \u003Cpr> --json statusCheckRollup,mergeStateStatus` directly and act on any FAILURE. A watcher that has produced nothing for a long stretch is a suspect, not a status.\n\nFor a merge-queue drain, prefer `scripts\u002Fmerge-cascade.ts` (it gates positively and merges on green); reach for `ci-watch.ts` when you need to block on one run\u002FPR and branch on the result.\n\n## Who runs the watcher\n\n`run_in_background` behaves the same for the orchestrator and for a sub-agent: a backgrounded Bash command persists across turns and re-invokes **its launcher** on exit. Both patterns below are valid.\n\n**Merge-on-green (the default).** The orchestrator runs the blocking watcher as its own `run_in_background` Bash task:\n\n1. **Enqueue:** append `{\"pr\":N,\"branch\":\"…\",\"thread\":\"…\",\"note\":\"…\"}` (optional `\"hold\":true`) to `.frizz\u002Fmerge-queue.jsonl`. Enqueue UNHELD only once the PR's FINAL head is pushed AND `gh pr edit \u003Cn> --add-label ci` has requested a run against it — a stale head can be green-but-wrong, and an unrequested one never goes green at all, so the queue would hold it until the cascade times out.\n2. **Watch:** the orchestrator runs `node scripts\u002Fmerge-cascade.ts --max-minutes 40` with `run_in_background: true`. It gates positively on the required `CI gate` (present + SUCCESS) + mergeable, merges `--squash --admin`, ff-pulls, dequeues, exits → re-invokes the orchestrator. It shares ci-watch's ghost carve-out (`scripts\u002Flib\u002Fci-rollup.ts`), so a still-running or failed REQUIRED gate always blocks and a red PR is never mis-merged.\n3. **Landing agents PUSH-THEN-EXIT** — they push, request CI with `gh pr edit \u003Cn> --add-label ci`, and report `pushed \u003Csha>, CI requested, queued`. They never watch.\n\n**Self-contained landing agent** (one agent traces push→merge): push the branch; request the run with `gh pr edit \u003Cn> --add-label ci`; launch `node scripts\u002Fmerge-cascade.ts --max-minutes 40` (or `ci-watch.ts`) for its OWN PR via `run_in_background: true`; end its turn; it is re-invoked when the command exits, reports merged\u002Fred, and iterates. **Do not preempt a landing agent's background watch** by checking CI yourself and merging manually mid-trace — that impatience is what breaks the flow.\n\n**Foreground chunk loop (fallback only)** — for an agent that must actively iterate and cannot rest:\n\n```bash\n# Bash tool: foreground (NOT run_in_background), timeout: 570000  (9.5 min, under the 600000 cap)\nnub scripts\u002Fci-watch.ts --pr \u003CN> --chunk          # --chunk caps the watch ~9 min and exits 2 with \"RERUN to continue\" if still pending\n#   exit 0 = green → act    exit 1 = red → fix + re-push    exit 2 = pending → RE-RUN the SAME command    exit 3 = error\n```\n\nWhile it exits 2, call it again — each chunk completes within the cap (no kill, no orphan). Blocking in the sub-agent's foreground is fine: it is backgrounded relative to the orchestrator. **A dispatch prompt for a self-gating landing agent must spell this loop out** — a sub-agent won't infer it.\n\nA `CronCreate` heartbeat (every ~4 min, one non-blocking `gh pr view` poll per queued PR) is a FALLBACK only if a background shell ever proves unreliable.\n","# Watching CI with the GitHub CLI\n\nWatching only reads, so it stays plain `gh`. The one write here, `gh pr edit \u003Cn> --add-label ci`, runs as `keyward --reason \"\u003Cthe task>\" -- gh pr edit …` on the maintainer's Mac.\n\n## The pitfall: raw watchers exit early\n\n`gh run watch \u003Cid> --exit-status` and `gh pr checks \u003Cpr> --watch` are not safe to arm right after a push \u002F tag \u002F PR-open:\n\n- **Premature exit while QUEUED.** With no jobs registered yet, gh sees \"nothing in progress\" and returns **exit 0** even though the run is still queued.\n- **Transient errors read as failure.** A mid-watch `HTTP 401: Bad credentials` (token refresh) or a 5xx exits non-zero, indistinguishable from a real CI failure.\n- **No native fix** — `--interval` only tunes the poll cadence.\n\n**Never trust a raw watcher's exit code alone.** Re-verify terminal status with `gh run view \u003Cid> --json status,conclusion` (done only when `status == \"completed\"`) or `gh pr view \u003Cpr> --json statusCheckRollup` (done only when every item is terminal). And always fail-fast — act on the first failing check, never wait for all checks to finish.\n\n## The blessed tool: `scripts\u002Fci-watch.ts`\n\nBlocks until the target is truly terminal, then exits with a trustworthy status. Dogfoods nub; runs under plain Node too.\n\n```bash\nnub  scripts\u002Fci-watch.ts --run \u003Crun-id> [--repo o\u002Fr] [--timeout \u003Cmin>]\nnode scripts\u002Fci-watch.ts --pr  \u003Cnumber> [--repo o\u002Fr] [--timeout \u003Cmin>]\n```\n\n- `--run \u003Crun-id>` — watch a workflow run (polls `gh run view --json status,conclusion,jobs`).\n- `--pr \u003Cnumber>` — watch a PR's check rollup (polls `gh pr view --json statusCheckRollup,…`).\n- `--repo \u003Cowner\u002Frepo>` — defaults to the current repo.\n- `--timeout \u003Cminutes>` — wall-clock cap before giving up as pending (default 45).\n- `--required \u003Cnames>` — comma-separated branch-protection check names to gate on (e.g. `--required \"CI gate\"`). Success fires the instant every required check is green; a ghost or a non-required check — pending *or* failed — never blocks, matching branch-protection semantics. Prefer it when you know the required check name.\n- `--no-progress \u003Cminutes>` — how long an unchanged incomplete set (all named checks green, only a ghost left) may sit before exiting 4 STUCK-but-safe (default 8).\n\nWhat it fixes: **waits for the target to EXIST** (not-found \u002F no-jobs-yet is \"keep polling,\" never \"done\"); polls authoritative terminal state; **fails fast** on the first FAILURE\u002FCANCELLED\u002FTIMED_OUT\u002F STARTUP_FAILURE; **never hangs on a ghost**; **tolerates transient** gh\u002FAPI errors (retried with exponential jittered backoff, 10s → cap 60s, 90s unauthenticated).\n\n### The ghost check — why a strict \"all checks terminal\" gate hangs\n\nGitHub occasionally registers a check-run that never reports a status: PENDING, nameless, forever. A watcher waiting for *every* rollup item to be terminal blocks indefinitely even though every real check is green. So a nameless \u002F never-terminating non-required check does not block a green verdict: once every named check is green and the incomplete set has been unchanged for `--no-progress` minutes, the watcher exits **4 (STUCK-but-safe)** and the caller `--admin` merges. A *named* pending check is never treated as a ghost, so a real in-flight check is never green-lit early.\n\n### Exit-code contract\n\n| code | meaning |\n| ---- | ------- |\n| 0 | completed AND all green |\n| 1 | a check\u002Fjob failed (the summary names which + the URL) |\n| 2 | required\u002Fnamed checks still NOT green after `--timeout` (genuinely stuck) |\n| 3 | usage \u002F target-unresolvable \u002F unrecoverable error |\n| 4 | STUCK-but-safe — required\u002Fnamed checks all green, but a ghost check will never terminate; safe to `--admin` merge (the caller decides) |\n\nThe final stdout line is a single self-describing summary, e.g. `CI-WATCH run 27972328590: SUCCESS (25 job(s) green)`, `CI-WATCH pr 73: FAILURE — check \"Test (ubuntu-latest, node 22.13)\" → FAILURE (https:\u002F\u002F…)`, or `CI-WATCH pr 327: STUCK — required\u002Fnamed checks GREEN (51), 1 non-terminal ghost\u002Fnon-required check(s): (unnamed); safe to --admin merge`.\n\n### NEVER pipe the watcher — a pipe discards the verdict you gate on\n\nThe exit code IS the contract, and a pipeline throws it away: in `ci-watch.ts … | tail -20`, `$?` is **tail's** status, so a **FAILED CI reads as SUCCESS**. The pipe also buffers stdout until the pipeline ends, so the log stays empty while the watcher runs.\n\n```bash\n# WRONG — $? is tail's, a red CI looks green, and no interim output\nnode scripts\u002Fci-watch.ts --pr 604 --repo nubjs\u002Fnub | tail -25; echo \"exit=$?\"\n\n# RIGHT — redirect, then gate on the watcher's OWN status\nnode scripts\u002Fci-watch.ts --pr 604 --repo nubjs\u002Fnub > \u002Ftmp\u002Fci604.log 2>&1; rc=$?\ntail -15 \u002Ftmp\u002Fci604.log; echo \"exit=$rc\"\n```\n\n`main()` warns on stderr when it detects a piped stdout (fd 1 is a FIFO for `| cmd`, not for `> file`), but redirect by default rather than relying on the warning. Bash `${PIPESTATUS[0]}` \u002F zsh `${pipestatus[1]}` recover the real status if a pipe is unavoidable.\n\n**Cross-check the rollup regardless of what the watcher says.** Read `gh pr view \u003Cpr> --json statusCheckRollup,mergeStateStatus` directly and act on any FAILURE. A watcher that has produced nothing for a long stretch is a suspect, not a status.\n\nFor a merge-queue drain, prefer `scripts\u002Fmerge-cascade.ts` (it gates positively and merges on green); reach for `ci-watch.ts` when you need to block on one run\u002FPR and branch on the result.\n\n## Who runs the watcher\n\n`run_in_background` behaves the same for the orchestrator and for a sub-agent: a backgrounded Bash command persists across turns and re-invokes **its launcher** on exit. Both patterns below are valid.\n\n**Merge-on-green (the default).** The orchestrator runs the blocking watcher as its own `run_in_background` Bash task:\n\n1. **Enqueue:** append `{\"pr\":N,\"branch\":\"…\",\"thread\":\"…\",\"note\":\"…\"}` (optional `\"hold\":true`) to `.frizz\u002Fmerge-queue.jsonl`. Enqueue UNHELD only once the PR's FINAL head is pushed AND `gh pr edit \u003Cn> --add-label ci` has requested a run against it — a stale head can be green-but-wrong, and an unrequested one never goes green at all, so the queue would hold it until the cascade times out.\n2. **Watch:** the orchestrator runs `node scripts\u002Fmerge-cascade.ts --max-minutes 40` with `run_in_background: true`. It gates positively on the required `CI gate` (present + SUCCESS) + mergeable, merges `--squash --admin`, ff-pulls, dequeues, exits → re-invokes the orchestrator. It shares ci-watch's ghost carve-out (`scripts\u002Flib\u002Fci-rollup.ts`), so a still-running or failed REQUIRED gate always blocks and a red PR is never mis-merged.\n3. **Landing agents PUSH-THEN-EXIT** — they push, request CI with `gh pr edit \u003Cn> --add-label ci`, and report `pushed \u003Csha>, CI requested, queued`. They never watch.\n\n**Self-contained landing agent** (one agent traces push→merge): push the branch; request the run with `gh pr edit \u003Cn> --add-label ci`; launch `node scripts\u002Fmerge-cascade.ts --max-minutes 40` (or `ci-watch.ts`) for its OWN PR via `run_in_background: true`; end its turn; it is re-invoked when the command exits, reports merged\u002Fred, and iterates. **Do not preempt a landing agent's background watch** by checking CI yourself and merging manually mid-trace — that impatience is what breaks the flow.\n\n**Foreground chunk loop (fallback only)** — for an agent that must actively iterate and cannot rest:\n\n```bash\n# Bash tool: foreground (NOT run_in_background), timeout: 570000  (9.5 min, under the 600000 cap)\nnub scripts\u002Fci-watch.ts --pr \u003CN> --chunk          # --chunk caps the watch ~9 min and exits 2 with \"RERUN to continue\" if still pending\n#   exit 0 = green → act    exit 1 = red → fix + re-push    exit 2 = pending → RE-RUN the SAME command    exit 3 = error\n```\n\nWhile it exits 2, call it again — each chunk completes within the cap (no kill, no orphan). Blocking in the sub-agent's foreground is fine: it is backgrounded relative to the orchestrator. **A dispatch prompt for a self-gating landing agent must spell this loop out** — a sub-agent won't infer it.\n\nA `CronCreate` heartbeat (every ~4 min, one non-blocking `gh pr view` poll per queued PR) is a FALLBACK only if a background shell ever proves unreliable.\n",{"name":5,"metadata":24,"description":7},{"internal":25},true,"main","9b734566fd36ceed8379f67a92291bc68af60801",".claude\u002Fskills\u002Fci-watch",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-watch",{"tool":41,"command":42},"bunx","bunx skills add nubjs\u002Fnub --skill ci-watch",{"tool":44,"command":45},"pnpm","pnpm dlx skills add nubjs\u002Fnub --skill ci-watch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fci-watch\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",[],[]]