[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SPFBZ0117NFHBTNG2WGAS":3,"skill-same:01M72SPFBZ0117NFHBTNG2WGAS":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72SPFBZ0117NFHBTNG2WGAS","issue-triage",null,"Triage a Deno GitHub issue — reproduce bugs, classify, label, and comment with findings. Use when asked to triage an issue or when an issue number\u002FURL is provided for triage.","nimbus\u002Fdeno","nimbus","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14984268?v=4","01M72SP53QDF5F25NWSQZM8EZT","01M72SP54V2Q98GYY2K0V32MP7",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Fissue-triage\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: issue-triage\ndescription: Triage a Deno GitHub issue — reproduce bugs, classify, label, and comment with findings. Use when asked to triage an issue or when an issue number\u002FURL is provided for triage.\nargument-hint: \u003Cissue-number-or-url>\nallowed-tools: Bash(gh *) Bash(deno *) Bash(git *) Bash(mktemp *) Bash(rm *) Bash(cat *) Read Write Glob Grep Agent\n---\n\n# Deno Issue Triage\n\nTriage issue `$ARGUMENTS` on the `denoland\u002Fdeno` repository.\n\n## Step 1: Read the issue\n\n```!\ngh issue view $ARGUMENTS --repo denoland\u002Fdeno --json number,title,body,author,labels,state,comments,createdAt,url\n```\n\n## Step 2: Classify the issue\n\nDetermine what kind of issue this is:\n\n- **Bug report** — something isn't working as expected\n- **Feature request \u002F suggestion** — a new capability or enhancement\n- **Question** — a usage question, not a bug\n- **Duplicate** — already reported (search closed and open issues with\n  `gh issue list --search \"keywords\" --state all`)\n- **Invalid** — not actionable, not a Deno issue, or insufficient info\n\nIf the issue is clearly a question, duplicate, or invalid, skip reproduction and\ngo straight to Step 5.\n\n## Step 3: Check for missing information\n\nA valid bug report needs:\n\n- Deno version (`deno --version` output)\n- Operating system\n- Reproduction steps or minimal reproduction code\n- Expected behavior vs actual behavior\n\nIf any of these are missing, label as `needs info` and comment asking the author\nto provide the missing details. Do not attempt reproduction without a clear\nrepro case.\n\n## Step 4: Reproduce the bug\n\nOnly attempt reproduction for bug reports that have a clear repro case.\n\n### Setup\n\nPrefer running reproductions inside a Docker container for isolation. Fall back\nto a local temp directory only if Docker is unavailable.\n\n**Docker (preferred):**\n\n```sh\n# Run repro with latest canary\ndocker run --rm -v \"$REPRO_DIR\":\u002Frepro -w \u002Frepro denoland\u002Fdeno:canary deno run repro.ts\n\n# Run repro with a specific version (e.g., 2.1.4)\ndocker run --rm -v \"$REPRO_DIR\":\u002Frepro -w \u002Frepro denoland\u002Fdeno:2.1.4 deno run repro.ts\n```\n\nUse `docker run --rm` so containers are cleaned up automatically. Mount the\nrepro files via `-v`.\n\n**Local fallback (if Docker is not available):**\n\n```sh\nREPRO_DIR=$(mktemp -d)\ndeno run \"$REPRO_DIR\u002Frepro.ts\"\n```\n\n### Get Deno versions\n\nTry to reproduce with both:\n\n1. **The version from the issue** (if specified) — to confirm the bug exists\n2. **Latest canary** — to check if it's already fixed\n\nUse the appropriate Docker image tag for each version (e.g.,\n`denoland\u002Fdeno:2.1.4`, `denoland\u002Fdeno:canary`).\n\nIf the issue specifies a particular Deno version and the bug does NOT reproduce\non canary, note that it may already be fixed. Check git log for relevant fixes.\n\n### Run the reproduction\n\n- Extract the reproduction code from the issue body\n- Write it to a local temp directory\n- Run it inside a Docker container (or locally as fallback) with the appropriate\n  `deno` subcommand and flags\n- Capture both stdout and stderr\n- Compare actual output against the expected behavior described in the issue\n\nIf the reproduction involves specific npm packages, `deno.json` config, or\nmulti-file setups, recreate the full environment as described.\n\n### Clean up\n\n```sh\nrm -rf \"$REPRO_DIR\"\n```\n\n### Record findings\n\nNote:\n\n- Does the bug reproduce on the reported version?\n- Does the bug reproduce on canary?\n- Any additional observations (e.g., different error message, partial fix,\n  related issues)\n\n## Step 5: Label the issue\n\nAdd labels based on your classification. Keep it minimal — usually a single area\nlabel is sufficient. Do not over-label.\n\n### Type labels (add one if applicable)\n\n| Label        | When to use                                         |\n| ------------ | --------------------------------------------------- |\n| `bug`        | Confirmed bug — always add for verified bug reports |\n| `feat`       | Accepted new feature                                |\n| `suggestion` | Feature request not yet accepted                    |\n| `question`   | Usage question                                      |\n| `duplicate`  | Duplicate of another issue                          |\n| `invalid`    | Not actionable                                      |\n| `panic`      | Deno panics\u002Fcrashes                                 |\n| `regression` | Something that used to work but is now broken       |\n\n### Area labels (add one that best matches)\n\n| Label                                                                                                                                  | Area                             |\n| -------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |\n| `node compat`                                                                                                                          | General Node.js compatibility    |\n| `node API`                                                                                                                             | Specific `node:*` module APIs    |\n| `ext\u002Fnode`, `ext\u002Ffs`, `ext\u002Fnet`, `ext\u002Fhttp`, `ext\u002Ffetch`, `ext\u002Fweb`, `ext\u002Fcrypto`, `ext\u002Fconsole`, `ext\u002Furl`, `ext\u002Fwebsocket`, `ext\u002Fkv` | Specific extension               |\n| `cli`                                                                                                                                  | CLI behavior, flags, subcommands |\n| `lsp`                                                                                                                                  | Language server                  |\n| `runtime`                                                                                                                              | Runtime crate                    |\n| `permissions`                                                                                                                          | Permission system                |\n| `compile`                                                                                                                              | `deno compile`                   |\n| `testing`                                                                                                                              | `deno test` and coverage         |\n| `task runner`                                                                                                                          | `deno task`                      |\n| `install`                                                                                                                              | `deno install` \u002F `deno add`      |\n| `tsc`                                                                                                                                  | TypeScript compiler              |\n| `types`                                                                                                                                | TypeScript type issues           |\n| `config`                                                                                                                               | `deno.json` configuration        |\n| `node resolution`                                                                                                                      | Node\u002Fnpm module resolution       |\n| `publish`                                                                                                                              | `deno publish`                   |\n| `lint`                                                                                                                                 | `deno lint`                      |\n| `wasm`                                                                                                                                 | WebAssembly                      |\n\n### Priority labels (add only when clearly warranted)\n\n| Label           | When to use                                 |\n| --------------- | ------------------------------------------- |\n| `high priority` | Severe impact, blocks users, security issue |\n| `quick fix`     | Obviously simple fix                        |\n\n### Adding labels\n\n```sh\ngh issue edit $ARGUMENTS --repo denoland\u002Fdeno --add-label \"bug\"\n```\n\nRemove the `needs triage` or `triage required 👀` label if present:\n\n```sh\ngh issue edit $ARGUMENTS --repo denoland\u002Fdeno --remove-label \"needs triage\" --remove-label \"triage required 👀\"\n```\n\n## Step 6: Comment on the issue\n\nPost a triage comment with your findings. Structure:\n\nFor **confirmed bugs**:\n\n```\nConfirmed on [version]. [Brief description of what you observed.]\n\n[If tested on canary: \"Also reproduces on canary.\" or \"Does not reproduce on canary — may already be fixed.\"]\n```\n\nFor **needs info**:\n\n```\nThanks for reporting. Could you provide [missing info]? This will help us investigate.\n```\n\nFor **duplicates**:\n\n```\nThis looks like a duplicate of #XXXX. Closing in favor of that issue.\n```\n\nFor **questions**:\n\n```\nThis is a usage question rather than a bug. [Brief answer or pointer to docs.] Closing this — feel free to ask on https:\u002F\u002Fdiscord.gg\u002Fdeno if you have more questions.\n```\n\n### Posting the comment\n\n```sh\ngh issue comment $ARGUMENTS --repo denoland\u002Fdeno --body \"comment text\"\n```\n\nClose the issue if it's a duplicate, question, or invalid:\n\n```sh\ngh issue close $ARGUMENTS --repo denoland\u002Fdeno --reason \"not planned\"\n```\n\n## Rules\n\n- Always confirm with the user before posting comments or modifying labels on\n  GitHub.\n- Do not close bug reports — only close duplicates, questions, and invalid\n  issues.\n- Keep labels minimal. One type label + one area label is usually enough.\n- Be kind to reporters. Thank them, especially first-time reporters.\n- If you cannot reproduce a bug, say so honestly — do not guess at causes.\n- If the reproduction requires permissions or resources you don't have access\n  to, note that and skip reproduction.\n- Never dismiss an issue without investigation.\n","# Deno Issue Triage\n\nTriage issue `$ARGUMENTS` on the `denoland\u002Fdeno` repository.\n\n## Step 1: Read the issue\n\n```!\ngh issue view $ARGUMENTS --repo denoland\u002Fdeno --json number,title,body,author,labels,state,comments,createdAt,url\n```\n\n## Step 2: Classify the issue\n\nDetermine what kind of issue this is:\n\n- **Bug report** — something isn't working as expected\n- **Feature request \u002F suggestion** — a new capability or enhancement\n- **Question** — a usage question, not a bug\n- **Duplicate** — already reported (search closed and open issues with\n  `gh issue list --search \"keywords\" --state all`)\n- **Invalid** — not actionable, not a Deno issue, or insufficient info\n\nIf the issue is clearly a question, duplicate, or invalid, skip reproduction and\ngo straight to Step 5.\n\n## Step 3: Check for missing information\n\nA valid bug report needs:\n\n- Deno version (`deno --version` output)\n- Operating system\n- Reproduction steps or minimal reproduction code\n- Expected behavior vs actual behavior\n\nIf any of these are missing, label as `needs info` and comment asking the author\nto provide the missing details. Do not attempt reproduction without a clear\nrepro case.\n\n## Step 4: Reproduce the bug\n\nOnly attempt reproduction for bug reports that have a clear repro case.\n\n### Setup\n\nPrefer running reproductions inside a Docker container for isolation. Fall back\nto a local temp directory only if Docker is unavailable.\n\n**Docker (preferred):**\n\n```sh\n# Run repro with latest canary\ndocker run --rm -v \"$REPRO_DIR\":\u002Frepro -w \u002Frepro denoland\u002Fdeno:canary deno run repro.ts\n\n# Run repro with a specific version (e.g., 2.1.4)\ndocker run --rm -v \"$REPRO_DIR\":\u002Frepro -w \u002Frepro denoland\u002Fdeno:2.1.4 deno run repro.ts\n```\n\nUse `docker run --rm` so containers are cleaned up automatically. Mount the\nrepro files via `-v`.\n\n**Local fallback (if Docker is not available):**\n\n```sh\nREPRO_DIR=$(mktemp -d)\ndeno run \"$REPRO_DIR\u002Frepro.ts\"\n```\n\n### Get Deno versions\n\nTry to reproduce with both:\n\n1. **The version from the issue** (if specified) — to confirm the bug exists\n2. **Latest canary** — to check if it's already fixed\n\nUse the appropriate Docker image tag for each version (e.g.,\n`denoland\u002Fdeno:2.1.4`, `denoland\u002Fdeno:canary`).\n\nIf the issue specifies a particular Deno version and the bug does NOT reproduce\non canary, note that it may already be fixed. Check git log for relevant fixes.\n\n### Run the reproduction\n\n- Extract the reproduction code from the issue body\n- Write it to a local temp directory\n- Run it inside a Docker container (or locally as fallback) with the appropriate\n  `deno` subcommand and flags\n- Capture both stdout and stderr\n- Compare actual output against the expected behavior described in the issue\n\nIf the reproduction involves specific npm packages, `deno.json` config, or\nmulti-file setups, recreate the full environment as described.\n\n### Clean up\n\n```sh\nrm -rf \"$REPRO_DIR\"\n```\n\n### Record findings\n\nNote:\n\n- Does the bug reproduce on the reported version?\n- Does the bug reproduce on canary?\n- Any additional observations (e.g., different error message, partial fix,\n  related issues)\n\n## Step 5: Label the issue\n\nAdd labels based on your classification. Keep it minimal — usually a single area\nlabel is sufficient. Do not over-label.\n\n### Type labels (add one if applicable)\n\n| Label        | When to use                                         |\n| ------------ | --------------------------------------------------- |\n| `bug`        | Confirmed bug — always add for verified bug reports |\n| `feat`       | Accepted new feature                                |\n| `suggestion` | Feature request not yet accepted                    |\n| `question`   | Usage question                                      |\n| `duplicate`  | Duplicate of another issue                          |\n| `invalid`    | Not actionable                                      |\n| `panic`      | Deno panics\u002Fcrashes                                 |\n| `regression` | Something that used to work but is now broken       |\n\n### Area labels (add one that best matches)\n\n| Label                                                                                                                                  | Area                             |\n| -------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |\n| `node compat`                                                                                                                          | General Node.js compatibility    |\n| `node API`                                                                                                                             | Specific `node:*` module APIs    |\n| `ext\u002Fnode`, `ext\u002Ffs`, `ext\u002Fnet`, `ext\u002Fhttp`, `ext\u002Ffetch`, `ext\u002Fweb`, `ext\u002Fcrypto`, `ext\u002Fconsole`, `ext\u002Furl`, `ext\u002Fwebsocket`, `ext\u002Fkv` | Specific extension               |\n| `cli`                                                                                                                                  | CLI behavior, flags, subcommands |\n| `lsp`                                                                                                                                  | Language server                  |\n| `runtime`                                                                                                                              | Runtime crate                    |\n| `permissions`                                                                                                                          | Permission system                |\n| `compile`                                                                                                                              | `deno compile`                   |\n| `testing`                                                                                                                              | `deno test` and coverage         |\n| `task runner`                                                                                                                          | `deno task`                      |\n| `install`                                                                                                                              | `deno install` \u002F `deno add`      |\n| `tsc`                                                                                                                                  | TypeScript compiler              |\n| `types`                                                                                                                                | TypeScript type issues           |\n| `config`                                                                                                                               | `deno.json` configuration        |\n| `node resolution`                                                                                                                      | Node\u002Fnpm module resolution       |\n| `publish`                                                                                                                              | `deno publish`                   |\n| `lint`                                                                                                                                 | `deno lint`                      |\n| `wasm`                                                                                                                                 | WebAssembly                      |\n\n### Priority labels (add only when clearly warranted)\n\n| Label           | When to use                                 |\n| --------------- | ------------------------------------------- |\n| `high priority` | Severe impact, blocks users, security issue |\n| `quick fix`     | Obviously simple fix                        |\n\n### Adding labels\n\n```sh\ngh issue edit $ARGUMENTS --repo denoland\u002Fdeno --add-label \"bug\"\n```\n\nRemove the `needs triage` or `triage required 👀` label if present:\n\n```sh\ngh issue edit $ARGUMENTS --repo denoland\u002Fdeno --remove-label \"needs triage\" --remove-label \"triage required 👀\"\n```\n\n## Step 6: Comment on the issue\n\nPost a triage comment with your findings. Structure:\n\nFor **confirmed bugs**:\n\n```\nConfirmed on [version]. [Brief description of what you observed.]\n\n[If tested on canary: \"Also reproduces on canary.\" or \"Does not reproduce on canary — may already be fixed.\"]\n```\n\nFor **needs info**:\n\n```\nThanks for reporting. Could you provide [missing info]? This will help us investigate.\n```\n\nFor **duplicates**:\n\n```\nThis looks like a duplicate of #XXXX. Closing in favor of that issue.\n```\n\nFor **questions**:\n\n```\nThis is a usage question rather than a bug. [Brief answer or pointer to docs.] Closing this — feel free to ask on https:\u002F\u002Fdiscord.gg\u002Fdeno if you have more questions.\n```\n\n### Posting the comment\n\n```sh\ngh issue comment $ARGUMENTS --repo denoland\u002Fdeno --body \"comment text\"\n```\n\nClose the issue if it's a duplicate, question, or invalid:\n\n```sh\ngh issue close $ARGUMENTS --repo denoland\u002Fdeno --reason \"not planned\"\n```\n\n## Rules\n\n- Always confirm with the user before posting comments or modifying labels on\n  GitHub.\n- Do not close bug reports — only close duplicates, questions, and invalid\n  issues.\n- Keep labels minimal. One type label + one area label is usually enough.\n- Be kind to reporters. Thank them, especially first-time reporters.\n- If you cannot reproduce a bug, say so honestly — do not guess at causes.\n- If the reproduction requires permissions or resources you don't have access\n  to, note that and skip reproduction.\n- Never dismiss an issue without investigation.\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Bash(gh *) Bash(deno *) Bash(git *) Bash(mktemp *) Bash(rm *) Bash(cat *) Read Write Glob Grep Agent","\u003Cissue-number-or-url>","nimbus\u002Fv2.9.7","1abfdad63da77afe1517efc0190063e49f479748",".claude\u002Fskills\u002Fissue-triage","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno","https:\u002F\u002Fgithub.com\u002Fnimbus","2026-10-02 00:53:17",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add nimbus\u002Fdeno --skill issue-triage",{"tool":37,"command":38},"bunx","bunx skills add nimbus\u002Fdeno --skill issue-triage",{"tool":40,"command":41},"pnpm","pnpm dlx skills add nimbus\u002Fdeno --skill issue-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Fissue-triage\u002FSKILL.md",true,[],[46,53,60,67,74],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M72SPTFW41HMSPDTBSTNNKNB","review-pr","Review a Deno runtime pull request for correctness, tests, security, and conventions. Use when asked to review a PR or when a PR number\u002FURL is provided for review.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Freview-pr\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72SPPBQ2WHE3WS0P806ZG4A","node-compat","Run a Node.js compatibility test, diagnose failures, and either fix the implementation, skip, or ignore the test. Use when asked to work on node compat tests.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Fnode-compat\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M72SPMSNW1GA7J1GQN6FYFK2","lint-js","Lint JS\u002FTS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Flint-js\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72SPKK1VMJQE7592P3E83W6","lint-all","Lint all code (Rust + JS\u002FTS). Use before opening a PR when Rust code was changed.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Flint-all\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M72SPDSPTKS7VBV45KEJAX6H","fmt","Format all code in the repository. Run before opening a PR or committing changes.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Ffmt\u002FSKILL.md",[],[]]