[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SPTFW41HMSPDTBSTNNKNB":3,"skill-same:01M72SPTFW41HMSPDTBSTNNKNB":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},"01M72SPTFW41HMSPDTBSTNNKNB","review-pr",null,"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.","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\u002Freview-pr\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: review-pr\ndescription: 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.\nargument-hint: \u003Cpr-number-or-url>\nallowed-tools: Bash(gh *) Bash(git *) Read Glob Grep Agent\n---\n\n# Deno PR Reviewer\n\nReview PR `$ARGUMENTS` on the `denoland\u002Fdeno` repository.\n\n## Step 1: Gather PR context\n\nFetch the PR metadata, diff, and comments:\n\n```!\ngh pr view $ARGUMENTS --json number,title,body,author,labels,state,reviewDecision,commits,files,isDraft,createdAt,url\n```\n\n```!\ngh pr diff $ARGUMENTS\n```\n\n```!\ngh pr view $ARGUMENTS --comments --json comments\n```\n\n```!\ngh pr checks $ARGUMENTS --json name,state,conclusion 2>\u002Fdev\u002Fnull || echo \"No checks found\"\n```\n\n## Step 2: Gate checks\n\nBefore reviewing code, check these gates. If any fail, flag them prominently at\nthe top of your review and do not approve.\n\n1. **CI status** — All checks must pass. Point the author to specific failing\n   checks. Known flaky tests (labeled `ci-test-flaky`) can be re-run.\n2. **PR title format** — Must follow `type(scope): description`. Types: `feat`,\n   `fix`, `perf`, `refactor`, `chore`, `docs`, `test`, `revert`, `BREAKING`.\n   Scope examples: `ext\u002Fnode`, `ext\u002Ffetch`, `cli`, `lsp`, `runtime`.\n3. **No force pushes** — PRs are squash-merged. Authors should push new commits,\n   not rewrite history.\n4. **Focused scope** — No drive-by cleanups or unrelated changes. Those belong\n   in separate PRs.\n5. **AI disclosure** — If the PR looks AI-generated (boilerplate-heavy, generic\n   comments, suspiciously broad) but has no disclosure, ask about it.\n6. **Linked issue (external contributors)** — If the PR author is not a\n   `denoland` org member, the PR must link to an issue. If there is no linked\n   issue, request changes and ask the author to open an issue and discuss the\n   change first.\n\n## Step 3: Code review\n\nRead every changed file in the diff. Use the repo tools (`Read`, `Grep`, `Glob`)\nto understand surrounding context when needed.\n\n### Rust code\n\n- **Correctness**: Edge cases handled? No `.unwrap()` on user-controlled data?\n- **Error handling**: Proper error types, meaningful messages, no swallowed\n  errors.\n- **Performance**: No unnecessary allocations\u002Fcopies, no blocking in async code.\n- **Safety**: No `unsafe` without strong justification. No command injection,\n  path traversal, or permission bypasses.\n- **Permissions**: New capabilities must go through Deno's permission system.\n  Watch `ext\u002Fnode\u002F` especially — Node.js APIs sometimes assume full access.\n- **Dependencies**: New Cargo deps need strong justification. Prefer existing\n  deps or stdlib.\n\n### JavaScript\u002FTypeScript code\n\n- **Node.js compatibility** (`ext\u002Fnode\u002F`): Does the implementation match Node.js\n  behavior? Check against Node.js docs and\u002For source code.\n- **Primordials**: Internal JS should use primordials\n  (`globalThis.__bootstrap.primordials`) to avoid prototype pollution. Built-in\n  methods must not be called on user-controlled objects without primordial\n  wrappers.\n- **Web standards**: Web API implementations should follow the relevant spec.\n  WPT coverage is preferred.\n- **Lazy loading**: All code should use lazy-loaded imports where possible to\n  reduce startup cost.\n\n### Tests\n\n- Every bug fix needs a test that would have caught the bug. Every feature needs\n  happy-path + edge-case tests.\n- Prefer unit tests over spec tests over integration tests. Only use spec tests\n  when the behavior requires CLI-level validation.\n- Spec tests live in `tests\u002Fspecs\u002F` using `__test__.jsonc`. Use `[WILDCARD]` for\n  non-deterministic output, `[UNORDERED_START]`\u002F`[UNORDERED_END]` for\n  non-deterministic ordering.\n- Tests must be deterministic — no race conditions, timing deps, or port\n  conflicts.\n\n### Security-sensitive areas\n\nPay extra attention to changes in:\n\n- `runtime\u002Fpermissions.rs` and permission checks throughout\n- `ext\u002Fnet\u002F`, `ext\u002Ffs\u002F` — network and filesystem access\n- `ext\u002Fnode\u002F` — needs its own permission checks\n- `cli\u002Ftools\u002Fcompile.rs` — standalone binary compilation\n- Any code that shells out or processes user-controlled paths\u002FURLs\n\n## Step 4: PR-type-specific checks\n\nApply additional checks based on the PR type:\n\n- **Node.js compat** (`ext\u002Fnode\u002F`): Verify behavior against Node.js docs and\u002For\n  source code, not just what \"seems right\". New polyfills must be registered in\n  `ext\u002Fnode\u002Fpolyfills\u002F01_require.js`.\n- **Performance**: Must include before\u002Fafter benchmarks or a clear argument for\n  the improvement. Watch for correctness regressions.\n- **Dependency updates**: Check changelog for breaking changes. Prioritize\n  security updates.\n- **WPT changes**: Verify passes are real, not just skipped assertions.\n  Expectation file updates must match actual results. Suggest `ci-wpt-test`\n  label if not present.\n- **CI\u002Frelease tooling**: Flag for `@bartlomieju` review — do not approve these\n  yourself.\n\n## Step 5: Write your review\n\nPost a review using `gh pr review`. Structure:\n\n1. **Summary** (1-2 sentences): What the PR does and your overall assessment.\n2. **Gate issues** (if any): Blocking problems that must be fixed.\n3. **Code comments**: Specific, actionable feedback referencing exact files and\n   lines. Use `nit:` prefix for non-blocking suggestions. Suggest fixes when\n   possible, not just \"this is wrong.\"\n4. **Verdict**: Approve, request changes, or comment.\n\n### Tone\n\n- Direct: \"This needs a test\" not \"It would be wonderful if we could add a test\n  here.\"\n- Kind: Thank contributors, especially first-timers. Assume good intent.\n- Helpful: If rejecting, show what a good version looks like.\n- Brief: If the contributor clearly knows what they're doing, keep it tight.\n\n### Posting the review\n\nPrefer inline comments on specific lines where possible. Use a single review\nwith both a summary body and inline comments:\n\n```\ngh api repos\u002Fdenoland\u002Fdeno\u002Fpulls\u002F{number}\u002Freviews -f event=COMMENT -f body=\"summary\" -f comments='[{\"path\":\"file.rs\",\"line\":42,\"body\":\"comment\"}]'\n```\n\nUse `event=APPROVE` or `event=REQUEST_CHANGES` as appropriate instead of\n`COMMENT`.\n\nFor simple reviews without inline comments, fall back to:\n\n```\ngh pr review $ARGUMENTS --comment --body \"review text\"\n```\n\n### Merge readiness\n\nYou do NOT have merge permissions. When a PR is ready:\n\n- For first-time contributors: comment\n  `@bartlomieju LGTM, needs maintainer signoff (first-time contributor)`\n- For regular contributors: comment `@bartlomieju this is ready to merge`\n\n## Rules\n\n- Never approve a PR with failing CI.\n- Never approve PRs that bypass the permission system.\n- Never approve large architectural changes without flagging for maintainer\n  discussion.\n- Do not bikeshed style if it passes the linter.\n- Do not request changes for things automated checks already enforce.\n- Always confirm with the user before posting any review comments to GitHub.\n","# Deno PR Reviewer\n\nReview PR `$ARGUMENTS` on the `denoland\u002Fdeno` repository.\n\n## Step 1: Gather PR context\n\nFetch the PR metadata, diff, and comments:\n\n```!\ngh pr view $ARGUMENTS --json number,title,body,author,labels,state,reviewDecision,commits,files,isDraft,createdAt,url\n```\n\n```!\ngh pr diff $ARGUMENTS\n```\n\n```!\ngh pr view $ARGUMENTS --comments --json comments\n```\n\n```!\ngh pr checks $ARGUMENTS --json name,state,conclusion 2>\u002Fdev\u002Fnull || echo \"No checks found\"\n```\n\n## Step 2: Gate checks\n\nBefore reviewing code, check these gates. If any fail, flag them prominently at\nthe top of your review and do not approve.\n\n1. **CI status** — All checks must pass. Point the author to specific failing\n   checks. Known flaky tests (labeled `ci-test-flaky`) can be re-run.\n2. **PR title format** — Must follow `type(scope): description`. Types: `feat`,\n   `fix`, `perf`, `refactor`, `chore`, `docs`, `test`, `revert`, `BREAKING`.\n   Scope examples: `ext\u002Fnode`, `ext\u002Ffetch`, `cli`, `lsp`, `runtime`.\n3. **No force pushes** — PRs are squash-merged. Authors should push new commits,\n   not rewrite history.\n4. **Focused scope** — No drive-by cleanups or unrelated changes. Those belong\n   in separate PRs.\n5. **AI disclosure** — If the PR looks AI-generated (boilerplate-heavy, generic\n   comments, suspiciously broad) but has no disclosure, ask about it.\n6. **Linked issue (external contributors)** — If the PR author is not a\n   `denoland` org member, the PR must link to an issue. If there is no linked\n   issue, request changes and ask the author to open an issue and discuss the\n   change first.\n\n## Step 3: Code review\n\nRead every changed file in the diff. Use the repo tools (`Read`, `Grep`, `Glob`)\nto understand surrounding context when needed.\n\n### Rust code\n\n- **Correctness**: Edge cases handled? No `.unwrap()` on user-controlled data?\n- **Error handling**: Proper error types, meaningful messages, no swallowed\n  errors.\n- **Performance**: No unnecessary allocations\u002Fcopies, no blocking in async code.\n- **Safety**: No `unsafe` without strong justification. No command injection,\n  path traversal, or permission bypasses.\n- **Permissions**: New capabilities must go through Deno's permission system.\n  Watch `ext\u002Fnode\u002F` especially — Node.js APIs sometimes assume full access.\n- **Dependencies**: New Cargo deps need strong justification. Prefer existing\n  deps or stdlib.\n\n### JavaScript\u002FTypeScript code\n\n- **Node.js compatibility** (`ext\u002Fnode\u002F`): Does the implementation match Node.js\n  behavior? Check against Node.js docs and\u002For source code.\n- **Primordials**: Internal JS should use primordials\n  (`globalThis.__bootstrap.primordials`) to avoid prototype pollution. Built-in\n  methods must not be called on user-controlled objects without primordial\n  wrappers.\n- **Web standards**: Web API implementations should follow the relevant spec.\n  WPT coverage is preferred.\n- **Lazy loading**: All code should use lazy-loaded imports where possible to\n  reduce startup cost.\n\n### Tests\n\n- Every bug fix needs a test that would have caught the bug. Every feature needs\n  happy-path + edge-case tests.\n- Prefer unit tests over spec tests over integration tests. Only use spec tests\n  when the behavior requires CLI-level validation.\n- Spec tests live in `tests\u002Fspecs\u002F` using `__test__.jsonc`. Use `[WILDCARD]` for\n  non-deterministic output, `[UNORDERED_START]`\u002F`[UNORDERED_END]` for\n  non-deterministic ordering.\n- Tests must be deterministic — no race conditions, timing deps, or port\n  conflicts.\n\n### Security-sensitive areas\n\nPay extra attention to changes in:\n\n- `runtime\u002Fpermissions.rs` and permission checks throughout\n- `ext\u002Fnet\u002F`, `ext\u002Ffs\u002F` — network and filesystem access\n- `ext\u002Fnode\u002F` — needs its own permission checks\n- `cli\u002Ftools\u002Fcompile.rs` — standalone binary compilation\n- Any code that shells out or processes user-controlled paths\u002FURLs\n\n## Step 4: PR-type-specific checks\n\nApply additional checks based on the PR type:\n\n- **Node.js compat** (`ext\u002Fnode\u002F`): Verify behavior against Node.js docs and\u002For\n  source code, not just what \"seems right\". New polyfills must be registered in\n  `ext\u002Fnode\u002Fpolyfills\u002F01_require.js`.\n- **Performance**: Must include before\u002Fafter benchmarks or a clear argument for\n  the improvement. Watch for correctness regressions.\n- **Dependency updates**: Check changelog for breaking changes. Prioritize\n  security updates.\n- **WPT changes**: Verify passes are real, not just skipped assertions.\n  Expectation file updates must match actual results. Suggest `ci-wpt-test`\n  label if not present.\n- **CI\u002Frelease tooling**: Flag for `@bartlomieju` review — do not approve these\n  yourself.\n\n## Step 5: Write your review\n\nPost a review using `gh pr review`. Structure:\n\n1. **Summary** (1-2 sentences): What the PR does and your overall assessment.\n2. **Gate issues** (if any): Blocking problems that must be fixed.\n3. **Code comments**: Specific, actionable feedback referencing exact files and\n   lines. Use `nit:` prefix for non-blocking suggestions. Suggest fixes when\n   possible, not just \"this is wrong.\"\n4. **Verdict**: Approve, request changes, or comment.\n\n### Tone\n\n- Direct: \"This needs a test\" not \"It would be wonderful if we could add a test\n  here.\"\n- Kind: Thank contributors, especially first-timers. Assume good intent.\n- Helpful: If rejecting, show what a good version looks like.\n- Brief: If the contributor clearly knows what they're doing, keep it tight.\n\n### Posting the review\n\nPrefer inline comments on specific lines where possible. Use a single review\nwith both a summary body and inline comments:\n\n```\ngh api repos\u002Fdenoland\u002Fdeno\u002Fpulls\u002F{number}\u002Freviews -f event=COMMENT -f body=\"summary\" -f comments='[{\"path\":\"file.rs\",\"line\":42,\"body\":\"comment\"}]'\n```\n\nUse `event=APPROVE` or `event=REQUEST_CHANGES` as appropriate instead of\n`COMMENT`.\n\nFor simple reviews without inline comments, fall back to:\n\n```\ngh pr review $ARGUMENTS --comment --body \"review text\"\n```\n\n### Merge readiness\n\nYou do NOT have merge permissions. When a PR is ready:\n\n- For first-time contributors: comment\n  `@bartlomieju LGTM, needs maintainer signoff (first-time contributor)`\n- For regular contributors: comment `@bartlomieju this is ready to merge`\n\n## Rules\n\n- Never approve a PR with failing CI.\n- Never approve PRs that bypass the permission system.\n- Never approve large architectural changes without flagging for maintainer\n  discussion.\n- Do not bikeshed style if it passes the linter.\n- Do not request changes for things automated checks already enforce.\n- Always confirm with the user before posting any review comments to GitHub.\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Bash(gh *) Bash(git *) Read Glob Grep Agent","\u003Cpr-number-or-url>","nimbus\u002Fv2.9.7","1abfdad63da77afe1517efc0190063e49f479748",".claude\u002Fskills\u002Freview-pr","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 review-pr",{"tool":37,"command":38},"bunx","bunx skills add nimbus\u002Fdeno --skill review-pr",{"tool":40,"command":41},"pnpm","pnpm dlx skills add nimbus\u002Fdeno --skill review-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Freview-pr\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},"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":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},"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":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},"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":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},"01M72SPFBZ0117NFHBTNG2WGAS","issue-triage","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.","https:\u002F\u002Fgithub.com\u002Fnimbus\u002Fdeno\u002Fblob\u002Fnimbus\u002Fv2.9.7\u002F.claude\u002Fskills\u002Fissue-triage\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",[],[]]