[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758455VXPNB2XGDFXN9Z4G6":3,"skill-same:01M758455VXPNB2XGDFXN9Z4G6":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},"01M758455VXPNB2XGDFXN9Z4G6","address-issue",null,"End-to-end playbook for working a GitHub issue (or bug-fix PR) on nubjs\u002Fnub: triage → acknowledge an external report with an \"Investigating\" comment → reproduce it yourself → SIZE it → fix it at that size (most issues are a small fix you just write — no investigation spike, no sub-agent fleet, no top-tier model) → open a PR that references the issue with `Closes #N` → on merge, comment the resolution → on release, comment the version + release link. Invoke (via the Skill tool) whenever you pick up an issue to work, or are asked to fix a reported bug. Encodes both the maintainer-hygiene conventions in AGENTS.md (so the reporter is acknowledged, the issue auto-closes on merge, and the loop closes when the fix ships) and the proportionality gate that keeps an ordinary bug from being worked like an audit.","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\u002Faddress-issue\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: address-issue\ndescription: >-\n  End-to-end playbook for working a GitHub issue (or bug-fix PR) on nubjs\u002Fnub:\n  triage → acknowledge an external report with an \"Investigating\" comment →\n  reproduce it yourself → SIZE it → fix it at that size (most issues are a small\n  fix you just write — no investigation spike, no sub-agent fleet, no top-tier\n  model) → open a PR that references the issue with `Closes #N` → on merge,\n  comment the resolution → on release, comment the version + release link. Invoke\n  (via the Skill tool) whenever you pick up an issue to work, or are asked to fix\n  a reported bug. Encodes both the maintainer-hygiene conventions in AGENTS.md\n  (so the reporter is acknowledged, the issue auto-closes on merge, and the loop\n  closes when the fix ships) and the proportionality gate that keeps an ordinary\n  bug from being worked like an audit.\nmetadata:\n  internal: true\n---\n\n# Addressing a nub issue end-to-end\n\nTaking a GitHub issue from \"reported\" to \"shipped and the reporter told.\" The hygiene rules here are mandatory, not courtesies — maintainer responsiveness on a public repo is a visible health signal.\n\nOn the maintainer's Mac, every `gh` below that writes (comment, close, `pr create`, `pr edit`) runs as `keyward --reason \"\u003Cthe task>\" -- gh …`. Reads stay plain `gh`.\n\n## Guardrails\n\n- **Tone is factual, neutral, professional** — never braggy, competitive, or over-promising. Invoke the `prose-writing` skill.\n- **A fix lands via the PR-from-a-worktree flow**, not directly on the shared `main` tree. Trivial doc\u002Ftypo fixes are the documented exception.\n- **Verify end-to-end before pushing** — run the pre-push local-verification loop. A green suite with a stubbed fix is worse than an unchecked one.\n- **Don't autonomously land a change to a default \u002F security posture \u002F product behavior \u002F API-config-env surface.** Those are recommend-only until the maintainer signs off. A mechanical, clearly-a-bug fix may land; a behavior decision routes back as a question.\n- **Work the issue at its ACTUAL size — the default is that you just fix it yourself.** Most issues are one clear cause and a small diff. Reaching for an investigation spike or a sub-agent fleet by reflex is the most common way this playbook is run wrong.\n\n## Step 1 — Triage: read the issue, the comments, and reproduce\n\n```bash\ngh issue view \u003Cn> --repo nubjs\u002Fnub --comments\n```\n\n- **Read the COMMENTS and the resolution history, not just the body.** The body says what someone wanted; the thread says what's true. A \"feature request\" can be a deliberate prior rejection; a \"bug\" can already be fixed on `main`.\n- **Classify it.** Genuine bug, usage question, feature request, duplicate, or already-fixed? Mechanical fix (land it) or a maintainer-owned surface (propose, get sign-off)?\n- **Reproduce empirically before reading source or deciding.** Build a minimal differential fixture — the behavior under nub vs the reference tool it claims parity with — in a throwaway `\u002Ftmp` dir. A divergence IS the finding.\n- **Do the reproduction YOURSELF.** It is a fixture and a couple of commands; a second-hand repro is a lead you then have to re-verify anyway.\n\n## Step 1b — Size it, and let the size pick the machinery\n\n**Default to the top row and move down only on evidence** — a cause you traced that turns out to be cross-cutting, a fix that touches a maintainer-owned surface. The issue's tone, label, or alarming title are not evidence.\n\n| Class | What it looks like | How you work it |\n| --- | --- | --- |\n| **Answer it** | usage question, duplicate, already fixed on `main`, working-as-intended, a docs or typo fix | Reply and close (Step 6). No worktree, no sub-agent. |\n| **Small fix** — *the common case* | one clear cause; a few lines across one or two files; no design call | Fix it yourself in a worktree. No sub-agent. Your own read of the diff plus the pre-push loop IS the review. |\n| **Real change** | several files, or logic whose knock-on effects you can't hold in your head, or a new test harness | Do it yourself or hand it to ONE implementation agent. Add ONE reviewer over the diff if the logic isn't self-evident. |\n| **Big** | a default \u002F security posture \u002F public surface, the resolver \u002F lockfile \u002F registry \u002F CAS, cross-platform behavior, or a genuine multi-prong audit | The full shape earns its keep: an owning agent, a multi-lens review split by dimension, top-tier models. |\n\n**Three or four Opus-high sub-agents on a small fix is a defect in how you ran the playbook, not thoroughness.** If you are about to dispatch, name which row you're in and what you found that puts you there — if you can't, you're in \"Small fix\" and you should just fix it.\n\nThe escalation mandates elsewhere in the repo — the fan-out rule and multi-lens self-review in AGENTS.local.md, the L1\u002FL2 shape in `implementation-thread` — describe the **Big** row. They are not a floor under every issue.\n\n## Step 2 — Acknowledge an external report immediately\n\nFor an EXTERNAL reporter (not a maintainer, not self-filed), post the acknowledgement the moment you start work. It is exactly one word:\n\n```bash\ngh issue comment \u003Cn> --repo nubjs\u002Fnub --body \"Investigating.\"\n```\n\nNo \"thanks for the report,\" no timeline, no preview of your hypothesis — a longer ack leaks half-formed theories and reads as noise. Internal\u002Fself-filed issues don't need this.\n\n**Every substantive comment is terse + factual per the `prose-writing` skill.** State what you found and what you did, in the fewest words that carry the facts. Never write \"previous comments were wrong\" or similar meta-commentary — prior comments are often a bot's. The `gh-comment-guard` PreToolUse hook blocks an over-long `gh issue\u002Fpr comment` \u002F `gh pr create` body; trim it, or set `NUB_ALLOW_LONG_COMMENT=1` only for a genuinely-needed longer body.\n\nIf triage shows it's not a bug, say so factually with the reason and close it per Step 6.\n\n## Step 3 — Fix it, at the size you sized it\n\n- **Small fix (most issues):** write it. The pre-push loop is the verification; your own read of your diff is the review. Don't dispatch anything.\n- **Real change:** one implementation agent, or yourself. One reviewer if the logic isn't self-evident.\n- **Big:** the orchestration methodology earns its keep (load the `orchestrator` skill by name) — you hold the goal set, dispatch model-tiered sub-agents, and the fix gets a multi-lens self-review scaled to blast radius.\n\nTier every agent you do dispatch by the judgment its task needs. A repro, a harvest, a doc update, or a CI watch is Sonnet or Haiku work; Opus is for the fix that lands.\n\nWork in an isolated worktree off `origin\u002Fmain`:\n\n```bash\ngit worktree add \u002Ftmp\u002Fnub-fix-\u003Cn> -b fix-issue-\u003Cn> origin\u002Fmain   # vendor\u002Faube comes along (plain in-tree files)\ncd \u002Ftmp\u002Fnub-fix-\u003Cn>\n# Build through the wrapper; never export CARGO_TARGET_DIR yourself — that opts\n# out of the CoW seeding that starts an isolated worktree warm (~14s) instead of\n# cold (~40 min).\nscripts\u002Frust-build.sh build -p nub-cli --profile fast\n```\n\nBefore pushing, run the pre-push local-verification loop: incremental build → the exact CI gates (`NUB_ALLOW_INCOMPLETE_RUNTIME=1 cargo clippy --all-targets --all-features -- -D warnings`, `cargo fmt --check`, scoped `cargo test`) → an e2e tmp-fixture run of the specific behavior → Docker for anything touching the global cache\u002Fconfig → promote a regression test for this bug into the suite. Get it green locally and push ONCE.\n\n## Step 3b — Update docs if the fix changes user-facing behavior\n\nIf a user observes the change — a flag's effect, a default, an error message, a formerly-broken feature that now works — update `site\u002Fcontent\u002Fdocs\u002F` in the same PR. The fix is not done until docs reflect it.\n\n## Step 4 — Open the PR, referencing the issue\n\nThe body MUST reference the issue: a closing keyword for a bug the PR resolves, `Refs #N` for related-but-not-resolving.\n\n```bash\ngit push -u origin fix-issue-\u003Cn>\ngh pr create --repo nubjs\u002Fnub \\\n  --title \"\u003Cconcise factual title>\" \\\n  --body \"$(cat \u003C\u003C'EOF'\n\u003CWhat the bug was and what the fix does, factually.>\n\nCloses #\u003Cn>\n\n\u003CVerification: the fixture\u002Fcommand you ran and its result.>\n\nhttps:\u002F\u002Fclaude.ai\u002Fcode\u002Fsession_\u003Cid>\nEOF\n)\"\n```\n\nReport the PR URL. Do NOT merge your own PR.\n\nPR CI is opt-in, so opening the pull request starts nothing. When the head is final, request the run and watch it:\n\n```sh\ngh pr edit \u003Cn> --add-label ci\nnub scripts\u002Fci-watch.ts --pr \u003Cn> --required \"CI gate\" --timeout 90\n```\n\n## Step 5 — On merge, comment the resolution\n\n`Closes #N` auto-closes the issue silently, so add a brief factual comment. Extremely concise — don't re-explain what was done or the process of doing it; the PR carries that. Thank an external reporter:\n\n```bash\ngh issue comment \u003Cn> --repo nubjs\u002Fnub --body \"Fixed in #\u003Cpr>, ships in the next release. Thanks for the report.\"\n```\n\n(Drop the thanks on an internal\u002Fself-filed issue.) If it did NOT auto-close (no closing keyword, or a non-fix resolution), close it explicitly with a comment — never silently:\n\n```bash\ngh issue close \u003Cn> --repo nubjs\u002Fnub --comment \"\u003Cone line: what resolved it, or why no code fix is needed>\"\n```\n\n## Step 6 — On release, comment the version + release link (mandatory)\n\nA fix merged is not a fix shipped. Keep it to the version + link; on an external contributor's PR, add a brief thanks:\n\n```bash\nREL=\"https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Freleases\u002Ftag\u002Fv\u003Cver>\"\ngh issue comment \u003Cn> --repo nubjs\u002Fnub --body \"Shipped in v\u003Cver>: $REL\"\ngh pr comment   \u003Cpr> --repo nubjs\u002Fnub --body \"Shipped in v\u003Cver>: $REL — thanks for the contribution.\"\n```\n\nIn practice the `release` skill's Step 5 executes this in bulk across the whole changeset; this documents the contract for a single issue.\n\n---\n\n## Quick reference\n\n| Step | Action |\n| --- | --- |\n| Triage | `gh issue view \u003Cn> --comments` · read the thread · reproduce it yourself with a differential fixture |\n| Size | Answer it · Small fix (default — just fix it, no sub-agents) · Real change (≤1 agent + ≤1 reviewer) · Big (full orchestrator shape) |\n| Acknowledge | `gh issue comment \u003Cn> --body \"Investigating.\"` — exactly that, nothing more (external only) |\n| Fix | in a worktree off `origin\u002Fmain`; machinery scaled to the size; pre-push loop green; add a regression test |\n| Docs | Update `site\u002Fcontent\u002Fdocs\u002F` if behavior changed — same PR as the fix |\n| PR | `gh pr create` with `Closes #\u003Cn>` in the body; report the URL; don't self-merge |\n| On merge | `gh issue comment \u003Cn> --body \"Fixed in #\u003Cpr>…\"` (or `gh issue close --comment` if not auto-closed) |\n| On release | `gh issue comment \u003Cn> --body \"Shipped in v\u003Cver>: \u003Crelease URL>\"` (via the `release` skill) |\n","# Addressing a nub issue end-to-end\n\nTaking a GitHub issue from \"reported\" to \"shipped and the reporter told.\" The hygiene rules here are mandatory, not courtesies — maintainer responsiveness on a public repo is a visible health signal.\n\nOn the maintainer's Mac, every `gh` below that writes (comment, close, `pr create`, `pr edit`) runs as `keyward --reason \"\u003Cthe task>\" -- gh …`. Reads stay plain `gh`.\n\n## Guardrails\n\n- **Tone is factual, neutral, professional** — never braggy, competitive, or over-promising. Invoke the `prose-writing` skill.\n- **A fix lands via the PR-from-a-worktree flow**, not directly on the shared `main` tree. Trivial doc\u002Ftypo fixes are the documented exception.\n- **Verify end-to-end before pushing** — run the pre-push local-verification loop. A green suite with a stubbed fix is worse than an unchecked one.\n- **Don't autonomously land a change to a default \u002F security posture \u002F product behavior \u002F API-config-env surface.** Those are recommend-only until the maintainer signs off. A mechanical, clearly-a-bug fix may land; a behavior decision routes back as a question.\n- **Work the issue at its ACTUAL size — the default is that you just fix it yourself.** Most issues are one clear cause and a small diff. Reaching for an investigation spike or a sub-agent fleet by reflex is the most common way this playbook is run wrong.\n\n## Step 1 — Triage: read the issue, the comments, and reproduce\n\n```bash\ngh issue view \u003Cn> --repo nubjs\u002Fnub --comments\n```\n\n- **Read the COMMENTS and the resolution history, not just the body.** The body says what someone wanted; the thread says what's true. A \"feature request\" can be a deliberate prior rejection; a \"bug\" can already be fixed on `main`.\n- **Classify it.** Genuine bug, usage question, feature request, duplicate, or already-fixed? Mechanical fix (land it) or a maintainer-owned surface (propose, get sign-off)?\n- **Reproduce empirically before reading source or deciding.** Build a minimal differential fixture — the behavior under nub vs the reference tool it claims parity with — in a throwaway `\u002Ftmp` dir. A divergence IS the finding.\n- **Do the reproduction YOURSELF.** It is a fixture and a couple of commands; a second-hand repro is a lead you then have to re-verify anyway.\n\n## Step 1b — Size it, and let the size pick the machinery\n\n**Default to the top row and move down only on evidence** — a cause you traced that turns out to be cross-cutting, a fix that touches a maintainer-owned surface. The issue's tone, label, or alarming title are not evidence.\n\n| Class | What it looks like | How you work it |\n| --- | --- | --- |\n| **Answer it** | usage question, duplicate, already fixed on `main`, working-as-intended, a docs or typo fix | Reply and close (Step 6). No worktree, no sub-agent. |\n| **Small fix** — *the common case* | one clear cause; a few lines across one or two files; no design call | Fix it yourself in a worktree. No sub-agent. Your own read of the diff plus the pre-push loop IS the review. |\n| **Real change** | several files, or logic whose knock-on effects you can't hold in your head, or a new test harness | Do it yourself or hand it to ONE implementation agent. Add ONE reviewer over the diff if the logic isn't self-evident. |\n| **Big** | a default \u002F security posture \u002F public surface, the resolver \u002F lockfile \u002F registry \u002F CAS, cross-platform behavior, or a genuine multi-prong audit | The full shape earns its keep: an owning agent, a multi-lens review split by dimension, top-tier models. |\n\n**Three or four Opus-high sub-agents on a small fix is a defect in how you ran the playbook, not thoroughness.** If you are about to dispatch, name which row you're in and what you found that puts you there — if you can't, you're in \"Small fix\" and you should just fix it.\n\nThe escalation mandates elsewhere in the repo — the fan-out rule and multi-lens self-review in AGENTS.local.md, the L1\u002FL2 shape in `implementation-thread` — describe the **Big** row. They are not a floor under every issue.\n\n## Step 2 — Acknowledge an external report immediately\n\nFor an EXTERNAL reporter (not a maintainer, not self-filed), post the acknowledgement the moment you start work. It is exactly one word:\n\n```bash\ngh issue comment \u003Cn> --repo nubjs\u002Fnub --body \"Investigating.\"\n```\n\nNo \"thanks for the report,\" no timeline, no preview of your hypothesis — a longer ack leaks half-formed theories and reads as noise. Internal\u002Fself-filed issues don't need this.\n\n**Every substantive comment is terse + factual per the `prose-writing` skill.** State what you found and what you did, in the fewest words that carry the facts. Never write \"previous comments were wrong\" or similar meta-commentary — prior comments are often a bot's. The `gh-comment-guard` PreToolUse hook blocks an over-long `gh issue\u002Fpr comment` \u002F `gh pr create` body; trim it, or set `NUB_ALLOW_LONG_COMMENT=1` only for a genuinely-needed longer body.\n\nIf triage shows it's not a bug, say so factually with the reason and close it per Step 6.\n\n## Step 3 — Fix it, at the size you sized it\n\n- **Small fix (most issues):** write it. The pre-push loop is the verification; your own read of your diff is the review. Don't dispatch anything.\n- **Real change:** one implementation agent, or yourself. One reviewer if the logic isn't self-evident.\n- **Big:** the orchestration methodology earns its keep (load the `orchestrator` skill by name) — you hold the goal set, dispatch model-tiered sub-agents, and the fix gets a multi-lens self-review scaled to blast radius.\n\nTier every agent you do dispatch by the judgment its task needs. A repro, a harvest, a doc update, or a CI watch is Sonnet or Haiku work; Opus is for the fix that lands.\n\nWork in an isolated worktree off `origin\u002Fmain`:\n\n```bash\ngit worktree add \u002Ftmp\u002Fnub-fix-\u003Cn> -b fix-issue-\u003Cn> origin\u002Fmain   # vendor\u002Faube comes along (plain in-tree files)\ncd \u002Ftmp\u002Fnub-fix-\u003Cn>\n# Build through the wrapper; never export CARGO_TARGET_DIR yourself — that opts\n# out of the CoW seeding that starts an isolated worktree warm (~14s) instead of\n# cold (~40 min).\nscripts\u002Frust-build.sh build -p nub-cli --profile fast\n```\n\nBefore pushing, run the pre-push local-verification loop: incremental build → the exact CI gates (`NUB_ALLOW_INCOMPLETE_RUNTIME=1 cargo clippy --all-targets --all-features -- -D warnings`, `cargo fmt --check`, scoped `cargo test`) → an e2e tmp-fixture run of the specific behavior → Docker for anything touching the global cache\u002Fconfig → promote a regression test for this bug into the suite. Get it green locally and push ONCE.\n\n## Step 3b — Update docs if the fix changes user-facing behavior\n\nIf a user observes the change — a flag's effect, a default, an error message, a formerly-broken feature that now works — update `site\u002Fcontent\u002Fdocs\u002F` in the same PR. The fix is not done until docs reflect it.\n\n## Step 4 — Open the PR, referencing the issue\n\nThe body MUST reference the issue: a closing keyword for a bug the PR resolves, `Refs #N` for related-but-not-resolving.\n\n```bash\ngit push -u origin fix-issue-\u003Cn>\ngh pr create --repo nubjs\u002Fnub \\\n  --title \"\u003Cconcise factual title>\" \\\n  --body \"$(cat \u003C\u003C'EOF'\n\u003CWhat the bug was and what the fix does, factually.>\n\nCloses #\u003Cn>\n\n\u003CVerification: the fixture\u002Fcommand you ran and its result.>\n\nhttps:\u002F\u002Fclaude.ai\u002Fcode\u002Fsession_\u003Cid>\nEOF\n)\"\n```\n\nReport the PR URL. Do NOT merge your own PR.\n\nPR CI is opt-in, so opening the pull request starts nothing. When the head is final, request the run and watch it:\n\n```sh\ngh pr edit \u003Cn> --add-label ci\nnub scripts\u002Fci-watch.ts --pr \u003Cn> --required \"CI gate\" --timeout 90\n```\n\n## Step 5 — On merge, comment the resolution\n\n`Closes #N` auto-closes the issue silently, so add a brief factual comment. Extremely concise — don't re-explain what was done or the process of doing it; the PR carries that. Thank an external reporter:\n\n```bash\ngh issue comment \u003Cn> --repo nubjs\u002Fnub --body \"Fixed in #\u003Cpr>, ships in the next release. Thanks for the report.\"\n```\n\n(Drop the thanks on an internal\u002Fself-filed issue.) If it did NOT auto-close (no closing keyword, or a non-fix resolution), close it explicitly with a comment — never silently:\n\n```bash\ngh issue close \u003Cn> --repo nubjs\u002Fnub --comment \"\u003Cone line: what resolved it, or why no code fix is needed>\"\n```\n\n## Step 6 — On release, comment the version + release link (mandatory)\n\nA fix merged is not a fix shipped. Keep it to the version + link; on an external contributor's PR, add a brief thanks:\n\n```bash\nREL=\"https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Freleases\u002Ftag\u002Fv\u003Cver>\"\ngh issue comment \u003Cn> --repo nubjs\u002Fnub --body \"Shipped in v\u003Cver>: $REL\"\ngh pr comment   \u003Cpr> --repo nubjs\u002Fnub --body \"Shipped in v\u003Cver>: $REL — thanks for the contribution.\"\n```\n\nIn practice the `release` skill's Step 5 executes this in bulk across the whole changeset; this documents the contract for a single issue.\n\n---\n\n## Quick reference\n\n| Step | Action |\n| --- | --- |\n| Triage | `gh issue view \u003Cn> --comments` · read the thread · reproduce it yourself with a differential fixture |\n| Size | Answer it · Small fix (default — just fix it, no sub-agents) · Real change (≤1 agent + ≤1 reviewer) · Big (full orchestrator shape) |\n| Acknowledge | `gh issue comment \u003Cn> --body \"Investigating.\"` — exactly that, nothing more (external only) |\n| Fix | in a worktree off `origin\u002Fmain`; machinery scaled to the size; pre-push loop green; add a regression test |\n| Docs | Update `site\u002Fcontent\u002Fdocs\u002F` if behavior changed — same PR as the fix |\n| PR | `gh pr create` with `Closes #\u003Cn>` in the body; report the URL; don't self-merge |\n| On merge | `gh issue comment \u003Cn> --body \"Fixed in #\u003Cpr>…\"` (or `gh issue close --comment` if not auto-closed) |\n| On release | `gh issue comment \u003Cn> --body \"Shipped in v\u003Cver>: \u003Crelease URL>\"` (via the `release` skill) |\n",{"name":5,"metadata":24,"description":7},{"internal":25},true,"main","9b734566fd36ceed8379f67a92291bc68af60801",".claude\u002Fskills\u002Faddress-issue",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 address-issue",{"tool":41,"command":42},"bunx","bunx skills add nubjs\u002Fnub --skill address-issue",{"tool":44,"command":45},"pnpm","pnpm dlx skills add nubjs\u002Fnub --skill address-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Faddress-issue\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",[],[]]