[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75851KXMFCRSATJQJK4E527":3,"skill-same:01M75851KXMFCRSATJQJK4E527":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":28,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M75851KXMFCRSATJQJK4E527","babysit",null,"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\u002Fbabysit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: babysit\ndescription: Bring one nubjs\u002Fnub pull request to merge-readiness — pull the inline reviews, verify each finding against the code, re-verify every fix round locally, fix CI, and loop. Invoke (via the Skill tool) when asked to babysit a PR, to get one merge-ready, or when you own a PR and are waiting on reviews or CI. Scope — babysit ENDS at merge-readiness and hands back; only an instruction to babysit it TO MERGE authorizes the merge, and that phrasing also delegates the readiness judgment, so decide rather than ask. Carries the traps that each cost a round trip: the GitHub CLI's PR-view JSON silently omits the inline review comments where the real findings live, the CI gate aggregator check registers LAST so a partial green rollup is not done, and PR CI is opt-in, so a pull request nobody labelled has no checks at all and a re-based or re-targeted branch keeps the checks of its old head.\n---\n\n# Babysit a PR (nubjs\u002Fnub)\n\nLoop: pull reviews → verify each finding → fix → re-verify locally → push → repeat. CI comes ONCE, at the end: PR CI is opt-in, so a push starts nothing and the run is requested with `gh pr edit \u003Cn> --add-label ci` when the head is final.\n\nOn the maintainer's Mac, every `gh` below that writes (`pr edit`, `pr close`, `pr reopen`, `pr merge`, the `resolveReviewThread` mutation) runs as `keyward --reason \"\u003Cthe task>\" -- gh …`. Reads stay plain `gh`.\n\n**Babysit ends at merge-ready.** Report that state and stop; the merge is the maintainer's. Only an instruction to babysit it *to merge* authorizes one — and that phrasing delegates the readiness judgment too, so decide against the criteria below instead of asking.\n\n## Reviews\n\nTwo bots review within minutes of every push: `pullfrog`, which posts a top-level review plus inline threads with a `\u003Cdetails>` write-up per finding, and `copilot-pull-request-reviewer`. The maintainer outranks both. A PR carrying no review was merged before they ran rather than approved by them, and only the review list distinguishes those.\n\nThe `gh pr view --json reviews,comments` form silently omits inline `pulls\u002F{n}\u002Fcomments`, which is where the actionable findings are. Use [`scripts\u002Fpr-reviews.ts`](..\u002F..\u002F..\u002Fscripts\u002Fpr-reviews.ts) — one GraphQL round trip for reviews, inline threads (id, resolved\u002Foutdated state, `file:line`) and PR conversation:\n\n```bash\nnub scripts\u002Fpr-reviews.ts \u003Cpr> | jq '.reviewThreads[] | select(.isResolved | not)'\n```\n\n## Triage\n\nSkip resolved and outdated threads first — an outdated one anchors a line a later push already rewrote.\n\nEvery finding is a hypothesis. Verify it against the code before acting; a confident write-up is the one that gets acted on unchecked. Null guards, \"just in case\" branches, and try\u002Fcatch around code that cannot throw are the slop shape [`AGENTS.md`](..\u002F..\u002F..\u002FAGENTS.md) names — reject those by default.\n\nReject with one factual line on the thread saying what you checked. Never ignore silently, and never reply conversationally to a bot. Load the `prose-writing` skill before writing any comment. Resolve each thread you address:\n\n```bash\ngh api graphql -f query='mutation($id:ID!){resolveReviewThread(input:{threadId:$id}){thread{isResolved}}}' -F id=\u003Cthread-id>\n```\n\n## Fix rounds\n\nA review-driven fix earns the same gate as the original change. Run `make verify`. For a behavior change, sweep adversarial fixtures against the branch's MERGE-BASE build ([`ad-hoc-test`](..\u002Fad-hoc-test\u002FSKILL.md)) — a run that only re-confirms the reported case tests your intent, not your fix. Escalate to the `impact-analysis` skill when the fix widened the blast radius. A one-line typo fix skips both.\n\nThen push. Pushing is free — PR CI is opt-in and nothing fires until it is asked for — so push each round as it lands and hold the CI request until the review loop is done. A requested run is roughly five workflows across eight platforms, and asking round after round is what starves the shared runner pool.\n\n## CI\n\nLook at `gh pr checks \u003CN>` before asking. The label is stripped within a minute of being added, so an empty label list says nothing about whether a run was requested, and a second request for the same head cancels the run already in flight — a full matrix thrown away (2026-09-19, #959: the maintainer had labelled it half an hour earlier, and the babysitter's request cancelled fifteen jobs). Checks already pending or running on the current head mean the run exists; watch that one.\n\nAsk for the run, then watch it. Both steps — the request is not optional, and until it lands the pull request has no checks at all:\n\n```bash\ngh pr edit \u003CN> --add-label ci      # requests CI against the current head; the label is removed again immediately\n                                   # use ci-full for resolution, the linker, the launcher's payload format, a shared type,\n                                   # or a change to a workflow only ci-full runs\nnub scripts\u002Fci-watch.ts --pr \u003CN> --required \"CI gate\" --timeout 90\n```\n\nPush a further commit after that and the run you were watching is stale — its checks belong to the old head, so ask again. `ci-watch` will not cover for a forgotten request: an empty or all-skipped rollup reports as pending, never green.\n\nThe `CI gate` job is an `if: always()` aggregator over every path-gated job, so it registers LAST: fifty green checks with it still pending means the run is not done. A raw `gh pr checks --watch` exits 0 while the run is queued with no jobs registered, so watch through [`scripts\u002Fci-watch.ts`](..\u002F..\u002F..\u002Fscripts\u002Fci-watch.ts).\n\nDiagnose red with [`ci-triage`](..\u002Fci-triage\u002FSKILL.md); a run whose rollup is `cancelled` can hold a job that failed, so the run-level conclusion misses real red.\n\nFix only what this PR caused, and never edit a workflow to make a check pass. A merge-blocking failure that looks unrelated is often a stale base — merge `main` in and re-run. The heavy legs fail for environment reasons too, so read the job log before calling one a regression:\n\n```\nDocker smoke · Windows matrix · daily-driver · native-deps\n```\n\n**Stacked PR.** After a rebase plus `gh pr edit --base main`, a LOW check count is a FALSE green. The `--base` edit fires no `synchronize` event, so every workflow gated on `pull_request: branches: [main]` never runs. Force the real matrix with `gh pr close \u003CN> && gh pr reopen \u003CN>`, then wait for it — a Rust PR carries around sixty checks.\n\n## Merge-ready\n\n- Mergeable: no conflicts, base current.\n- The `CI gate` check is green, or every failure is investigated and written up as unrelated.\n- Every valid finding is addressed, or rejected with reasoning on the thread.\n- Threads resolved.\n- The body carries `Closes #N` if the PR resolves an issue. Without it the issue stays silently open after the merge; `gh pr edit \u003CN> --body` fixes it.\n\nReport that state and stop here, unless the instruction was to merge.\n\n## Merging\n\nThe `Main` ruleset blocks `update` on `main`, so a plain merge fails with `the base branch policy prohibits the merge`, and auto-merge is disabled repo-wide. That ruleset sets no required status checks either, so nothing server-side stops a red merge. The flag below bypasses the protection rule, not the judgment — confirm `CI gate` yourself first.\n\n```bash\ngh pr merge \u003CN> --squash --admin\ngit -C \u003Cshared-tree> fetch origin && git -C \u003Cshared-tree> merge --ff-only origin\u002Fmain  # never pull --ff-only\ngit push origin --delete \u003Cbranch> && git branch -D \u003Cbranch>\ngit worktree remove \u003Cdir> --force\n```\n\nThe shared tree always carries a sibling's uncommitted work, so `pull --ff-only` runs rebase's precondition check and aborts on any dirty file. For a queue of approved PRs, [`scripts\u002Fmerge-cascade.ts`](..\u002F..\u002F..\u002Fscripts\u002Fmerge-cascade.ts) does all of the above per entry.\n","# Babysit a PR (nubjs\u002Fnub)\n\nLoop: pull reviews → verify each finding → fix → re-verify locally → push → repeat. CI comes ONCE, at the end: PR CI is opt-in, so a push starts nothing and the run is requested with `gh pr edit \u003Cn> --add-label ci` when the head is final.\n\nOn the maintainer's Mac, every `gh` below that writes (`pr edit`, `pr close`, `pr reopen`, `pr merge`, the `resolveReviewThread` mutation) runs as `keyward --reason \"\u003Cthe task>\" -- gh …`. Reads stay plain `gh`.\n\n**Babysit ends at merge-ready.** Report that state and stop; the merge is the maintainer's. Only an instruction to babysit it *to merge* authorizes one — and that phrasing delegates the readiness judgment too, so decide against the criteria below instead of asking.\n\n## Reviews\n\nTwo bots review within minutes of every push: `pullfrog`, which posts a top-level review plus inline threads with a `\u003Cdetails>` write-up per finding, and `copilot-pull-request-reviewer`. The maintainer outranks both. A PR carrying no review was merged before they ran rather than approved by them, and only the review list distinguishes those.\n\nThe `gh pr view --json reviews,comments` form silently omits inline `pulls\u002F{n}\u002Fcomments`, which is where the actionable findings are. Use [`scripts\u002Fpr-reviews.ts`](..\u002F..\u002F..\u002Fscripts\u002Fpr-reviews.ts) — one GraphQL round trip for reviews, inline threads (id, resolved\u002Foutdated state, `file:line`) and PR conversation:\n\n```bash\nnub scripts\u002Fpr-reviews.ts \u003Cpr> | jq '.reviewThreads[] | select(.isResolved | not)'\n```\n\n## Triage\n\nSkip resolved and outdated threads first — an outdated one anchors a line a later push already rewrote.\n\nEvery finding is a hypothesis. Verify it against the code before acting; a confident write-up is the one that gets acted on unchecked. Null guards, \"just in case\" branches, and try\u002Fcatch around code that cannot throw are the slop shape [`AGENTS.md`](..\u002F..\u002F..\u002FAGENTS.md) names — reject those by default.\n\nReject with one factual line on the thread saying what you checked. Never ignore silently, and never reply conversationally to a bot. Load the `prose-writing` skill before writing any comment. Resolve each thread you address:\n\n```bash\ngh api graphql -f query='mutation($id:ID!){resolveReviewThread(input:{threadId:$id}){thread{isResolved}}}' -F id=\u003Cthread-id>\n```\n\n## Fix rounds\n\nA review-driven fix earns the same gate as the original change. Run `make verify`. For a behavior change, sweep adversarial fixtures against the branch's MERGE-BASE build ([`ad-hoc-test`](..\u002Fad-hoc-test\u002FSKILL.md)) — a run that only re-confirms the reported case tests your intent, not your fix. Escalate to the `impact-analysis` skill when the fix widened the blast radius. A one-line typo fix skips both.\n\nThen push. Pushing is free — PR CI is opt-in and nothing fires until it is asked for — so push each round as it lands and hold the CI request until the review loop is done. A requested run is roughly five workflows across eight platforms, and asking round after round is what starves the shared runner pool.\n\n## CI\n\nLook at `gh pr checks \u003CN>` before asking. The label is stripped within a minute of being added, so an empty label list says nothing about whether a run was requested, and a second request for the same head cancels the run already in flight — a full matrix thrown away (2026-09-19, #959: the maintainer had labelled it half an hour earlier, and the babysitter's request cancelled fifteen jobs). Checks already pending or running on the current head mean the run exists; watch that one.\n\nAsk for the run, then watch it. Both steps — the request is not optional, and until it lands the pull request has no checks at all:\n\n```bash\ngh pr edit \u003CN> --add-label ci      # requests CI against the current head; the label is removed again immediately\n                                   # use ci-full for resolution, the linker, the launcher's payload format, a shared type,\n                                   # or a change to a workflow only ci-full runs\nnub scripts\u002Fci-watch.ts --pr \u003CN> --required \"CI gate\" --timeout 90\n```\n\nPush a further commit after that and the run you were watching is stale — its checks belong to the old head, so ask again. `ci-watch` will not cover for a forgotten request: an empty or all-skipped rollup reports as pending, never green.\n\nThe `CI gate` job is an `if: always()` aggregator over every path-gated job, so it registers LAST: fifty green checks with it still pending means the run is not done. A raw `gh pr checks --watch` exits 0 while the run is queued with no jobs registered, so watch through [`scripts\u002Fci-watch.ts`](..\u002F..\u002F..\u002Fscripts\u002Fci-watch.ts).\n\nDiagnose red with [`ci-triage`](..\u002Fci-triage\u002FSKILL.md); a run whose rollup is `cancelled` can hold a job that failed, so the run-level conclusion misses real red.\n\nFix only what this PR caused, and never edit a workflow to make a check pass. A merge-blocking failure that looks unrelated is often a stale base — merge `main` in and re-run. The heavy legs fail for environment reasons too, so read the job log before calling one a regression:\n\n```\nDocker smoke · Windows matrix · daily-driver · native-deps\n```\n\n**Stacked PR.** After a rebase plus `gh pr edit --base main`, a LOW check count is a FALSE green. The `--base` edit fires no `synchronize` event, so every workflow gated on `pull_request: branches: [main]` never runs. Force the real matrix with `gh pr close \u003CN> && gh pr reopen \u003CN>`, then wait for it — a Rust PR carries around sixty checks.\n\n## Merge-ready\n\n- Mergeable: no conflicts, base current.\n- The `CI gate` check is green, or every failure is investigated and written up as unrelated.\n- Every valid finding is addressed, or rejected with reasoning on the thread.\n- Threads resolved.\n- The body carries `Closes #N` if the PR resolves an issue. Without it the issue stays silently open after the merge; `gh pr edit \u003CN> --body` fixes it.\n\nReport that state and stop here, unless the instruction was to merge.\n\n## Merging\n\nThe `Main` ruleset blocks `update` on `main`, so a plain merge fails with `the base branch policy prohibits the merge`, and auto-merge is disabled repo-wide. That ruleset sets no required status checks either, so nothing server-side stops a red merge. The flag below bypasses the protection rule, not the judgment — confirm `CI gate` yourself first.\n\n```bash\ngh pr merge \u003CN> --squash --admin\ngit -C \u003Cshared-tree> fetch origin && git -C \u003Cshared-tree> merge --ff-only origin\u002Fmain  # never pull --ff-only\ngit push origin --delete \u003Cbranch> && git branch -D \u003Cbranch>\ngit worktree remove \u003Cdir> --force\n```\n\nThe shared tree always carries a sibling's uncommitted work, so `pull --ff-only` runs rebase's precondition check and aborts on any dirty file. For a queue of approved PRs, [`scripts\u002Fmerge-cascade.ts`](..\u002F..\u002F..\u002Fscripts\u002Fmerge-cascade.ts) does all of the above per entry.\n",{},"main","9b734566fd36ceed8379f67a92291bc68af60801",".claude\u002Fskills\u002Fbabysit",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":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add nubjs\u002Fnub --skill babysit",{"tool":38,"command":39},"bunx","bunx skills add nubjs\u002Fnub --skill babysit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add nubjs\u002Fnub --skill babysit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbabysit\u002FSKILL.md",true,[],[47,53,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M758BSH88RVXBG8TPCT427TY","nub","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002Fskills\u002Fnub\u002FSKILL.md",[],[],{"skillNo":54,"name":49,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"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",[],[]]