[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TXK6TY56QRDJFN02PGS5Z":3,"skill-same:01M77TXK6TY56QRDJFN02PGS5Z":166},{"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":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M77TXK6TY56QRDJFN02PGS5Z","nodejs-core",null,"Contributes to and debugs Node.js core, including nodejs\u002Fnode commit and PR tone, contribution workflows, native crashes, V8 performance, node-gyp builds, N-API bindings, and libuv issues. Use when drafting or reviewing a Node.js core commit or pull request, working in nodejs\u002Fnode, or diagnosing C++ addons, binding.gyp failures, segfaults, native leaks, V8 deoptimizations, and event-loop internals.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Contributes to and debugs Node.js core, including nodejs\u002Fnode commit and PR tone, contribution workflows, native crashes, V8 performance, node-gyp builds, N-API bindings, and libuv issues. Use when drafting or reviewing a Node.js core commit or pull request, working in nodejs\u002Fnode, or diagnosing C++ addons, binding.gyp failures, segfaults, native leaks, V8 deoptimizations, and event-loop internals.\"\nmetadata: {\"tags\":\"nodejs, nodejs-core, contributing, commit-message, pull-request, v8, libuv, cpp, native-addons, performance, debugging, internals\"}\n---\n## When to use\n\nUse this skill when you need deep Node.js internals expertise, including:\n- C++ addon development\n- V8 engine debugging\n- libuv event loop issues\n- Build system problems\n- Compilation failures\n- Performance optimization at the engine level\n- Understanding Node.js core architecture\n- Writing or reviewing `nodejs\u002Fnode` commits and pull request descriptions\n\n## How to use\n\nRead individual rule files for detailed explanations and code examples:\n\n### V8 Engine\n\n- [rules\u002Fv8-garbage-collection.md](rules\u002Fv8-garbage-collection.md) - Scavenger, Mark-Sweep, Mark-Compact, generational GC\n- [rules\u002Fv8-hidden-classes.md](rules\u002Fv8-hidden-classes.md) - Hidden classes, inline caching, optimization\n- [rules\u002Fv8-jit-compilation.md](rules\u002Fv8-jit-compilation.md) - TurboFan, optimization\u002Fdeoptimization patterns\n\n### libuv\n\n- [rules\u002Flibuv-event-loop.md](rules\u002Flibuv-event-loop.md) - Event loop phases, timers, I\u002FO, idle, check, close\n- [rules\u002Flibuv-thread-pool.md](rules\u002Flibuv-thread-pool.md) - Thread pool size, blocking operations, UV_THREADPOOL_SIZE\n- [rules\u002Flibuv-async-io.md](rules\u002Flibuv-async-io.md) - Async I\u002FO patterns, handles, requests\n\n### Native Addons\n\n- [rules\u002Fnapi.md](rules\u002Fnapi.md) - N-API development, ABI stability, async workers\n- [rules\u002Fnode-addon-api.md](rules\u002Fnode-addon-api.md) - C++ wrapper patterns, best practices\n- [rules\u002Fnative-memory.md](rules\u002Fnative-memory.md) - Buffer handling, external memory, prevent leaks\n\n### Core Modules Internals\n\n- [rules\u002Fstreams-internals.md](rules\u002Fstreams-internals.md) - How Node.js streams work at C++ level\n- [rules\u002Fnet-internals.md](rules\u002Fnet-internals.md) - TCP\u002FUDP implementation, socket handling\n- [rules\u002Ffs-internals.md](rules\u002Ffs-internals.md) - libuv fs operations, sync vs async\n- [rules\u002Fcrypto-internals.md](rules\u002Fcrypto-internals.md) - OpenSSL integration, performance considerations\n- [rules\u002Fchild-process-internals.md](rules\u002Fchild-process-internals.md) - IPC, spawn, fork implementation\n- [rules\u002Fworker-threads-internals.md](rules\u002Fworker-threads-internals.md) - SharedArrayBuffer, Atomics, MessageChannel\n\n### JavaScript Internals\n\n- [rules\u002Fprimordials.md](rules\u002Fprimordials.md) - **Using primordials to prevent prototype pollution (required for `lib\u002Finternal\u002F`)**\n\n### Build & Contributing\n\n- [rules\u002Fbuild-and-test-workflow.md](rules\u002Fbuild-and-test-workflow.md) - **The edit-build-lint-test cycle (start here)**\n- [rules\u002Fpre-commit-lint.md](rules\u002Fpre-commit-lint.md) - **Mandatory lint, format, and `core-validate-commit` gate for every commit so CI passes first time**\n- [rules\u002Fconfigure.md](rules\u002Fconfigure.md) - `.\u002Fconfigure` flags for debug builds, ASan, Ninja, etc.\n- [rules\u002Fbuild-system.md](rules\u002Fbuild-system.md) - gyp, ninja, make, cross-platform compilation\n- [rules\u002Fcli-options.md](rules\u002Fcli-options.md) - Adding CLI options and gating experimental modules\n- [rules\u002Fcontributing.md](rules\u002Fcontributing.md) - How to contribute to Node.js core, the process\n- [rules\u002Fcommit-and-pr-guideline.md](rules\u002Fcommit-and-pr-guideline.md) - Commit message and PR description style, trailers, DCO sign-off, and validation\n- [rules\u002Freviewing-prs.md](rules\u002Freviewing-prs.md) - Reviewing PRs for correctness, clarity, and contribution quality\n\n### Documentation\n\n- [rules\u002Fdocumentation.md](rules\u002Fdocumentation.md) - **Updating doc\u002Fapi\u002F*.md files: structure, link ordering, error docs, code example constraints**\n\n### Debugging & Profiling\n\n- [rules\u002Fdebugging-native.md](rules\u002Fdebugging-native.md) - gdb, lldb, debugging C++ addons\n- [rules\u002Fprofiling-v8.md](rules\u002Fprofiling-v8.md) - --prof, --trace-opt, --trace-deopt, flame graphs\n- [rules\u002Fmemory-debugging.md](rules\u002Fmemory-debugging.md) - Heap snapshots, memory leak detection\n\n## Instructions\n\n### Node.js contribution writing\n\nWhen drafting a `nodejs\u002Fnode` commit or pull request, read\n[rules\u002Fcommit-and-pr-guideline.md](rules\u002Fcommit-and-pr-guideline.md).\nUse terse subsystem-prefixed titles and plain, matter-of-fact prose. Lead with\nconcrete behavior, explain the reason for the change, and omit hype, canned\nheadings, file-by-file narration, and unsupported claims. Include the\ncontributor's DCO sign-off, and never add `PR-URL:` or `Reviewed-By:` — those\nare added when the change lands. Validate the result with\n`npx core-validate-commit --no-validate-metadata \u003Csha>` in the `nodejs\u002Fnode`\ncheckout.\n\n### MANDATORY: Rebuild before testing\n\nNode.js embeds `lib\u002F` JavaScript files into the binary at compile time via\n`js2c`. **After ANY change to `src\u002F` or `lib\u002F`, you MUST rebuild before\nrunning tests.** Without a rebuild, tests run against stale code and results\nare meaningless.\n\n```\nedit src\u002F or lib\u002F  →  make -j$(nproc)  →  make lint  →  then test\n```\n\nNever skip the rebuild step. Never run `.\u002Fnode test\u002F...` after editing\nwithout building first.\n\nBefore starting work, **ask the user** about their build configuration\n(Make vs Ninja, debug vs release, what configure flags they use). Do not\nassume a specific setup. Most of the time, `.\u002Fconfigure` has already been\nrun and only `make -j$(nproc)` is needed to rebuild.\n\n### MANDATORY: Lint and format before every commit\n\nNode.js runs a `Linters` CI workflow on every non-draft pull request, and on\nUnix `make test` runs **no** linters. Run `make lint` before each `git\ncommit` — plus `make format-cpp` for C++ changes — so the lint jobs pass on\nthe first CI run instead of costing a force-push and another full cycle.\n\n```bash\nmake -j$(nproc)                                        # rebuild first\nmake lint                                              # JS, C++, MD, docs, YAML\n\n# C++ changes only — use the merge-base form, which is what CI checks:\nCLANG_FORMAT_START=\"$(git merge-base HEAD upstream\u002Fmain)\" make format-cpp\ngit --no-pager diff --exit-code                        # must be empty\n\ngit add -A && git commit -s                            # -s is mandatory\nnpx core-validate-commit --no-validate-metadata HEAD\n```\n\nNever skip a step because the change looks trivial, and never commit with\n\"will fix lint in a follow-up\".\n\n**Bare `make format-cpp` is not enough.** It defaults to\n`CLANG_FORMAT_START=HEAD` and formats only *staged* changes, while the\n`format-cpp` CI job formats everything from the merge base and fails on any\nresulting diff — so unformatted code committed earlier in the branch passes\nlocally and fails in CI. Always pass the merge-base form shown above.\n\n**Every commit must be created with `git commit -s`.** The `-s` flag adds the\n`Signed-off-by:` trailer certifying the Developer Certificate of Origin.\nWithout it the `signed-off-by` rule of `core-validate-commit` fails and the PR\ncannot land. The sign-off must be the human contributor's name and email —\nnever sign off with a tool or AI identity, and never fabricate someone else's.\nIf you forget it, amend with `git commit --amend --signoff`.\n\n`make lint` runs `lint-js`, `lint-cpp`, `lint-addon-docs`, `lint-md`, and\n`lint-yaml` — it does not cover every CI lint job. Python (`make lint-py`),\nshell (`tools\u002Flint-sh.mjs .`), C++ formatting, and commit-message validation\nare separate jobs. See [rules\u002Fpre-commit-lint.md](rules\u002Fpre-commit-lint.md)\nfor the full gate and the CI-job-to-command mapping.\n\nValidate every commit message with `core-validate-commit`, always with\n`--no-validate-metadata` — metadata validation is on by default and enforces\ntrailers that only exist after landing. **Never add `PR-URL:` or\n`Reviewed-By:` to a commit you author**; the landing process adds them.\n\nSee [rules\u002Fbuild-and-test-workflow.md](rules\u002Fbuild-and-test-workflow.md)\nfor the full workflow including configure flags, lint targets, and test\ncommands.\n\n### Core knowledge domains\n\nApply deep knowledge of Node.js internals across these domains:\n\n- **Core architecture**: Node.js core modules and their C++ implementations, V8 GC and JIT, libuv event loop mechanics, thread pool behavior, startup\u002Fmodule-loading lifecycle\n- **Native development**: N-API, node-addon-api, and NAN addon development; V8 C++ API handle management; memory safety; native debugging with gdb\u002Flldb\n- **Build systems**: node-gyp, gyp, ninja, make; cross-platform compilation; linker errors; dependency issues; platform-specific considerations (Windows, macOS, Linux, embedded)\n- **Performance & debugging**: Event loop profiling, memory leak detection in JS and native code, CPU flame graphs, V8 optimization\u002Fdeoptimization tracing\n\n### Quick-reference debugging commands\n\n**V8 optimization tracing:**\n```bash\nnode --trace-opt --trace-deopt script.js\n# Checkpoint: confirm no unexpected deoptimization warnings before proceeding to profiling\nnode --prof script.js && node --prof-process isolate-*.log > processed.txt\n```\n\n**Event loop lag detection:**\n```bash\nnode --trace-event-categories v8,node,node.async_hooks script.js\n```\n\n**Native addon debugging (gdb):**\n```bash\ngdb --args node --napi-modules .\u002Fbuild\u002FRelease\u002Faddon.node\n# Inside gdb:\nrun\nbt        # backtrace on crash\n# Checkpoint: verify backtrace shows the expected call site before applying a fix\n```\n\n**Heap snapshot for memory leaks:**\n```bash\nnode --inspect script.js   # then open chrome:\u002F\u002Finspect, take heap snapshot\n# Checkpoint: compare two consecutive heap snapshots to confirm leak growth before and after the fix; run valgrind --leak-check=full node addon_test.js to confirm no native leaks remain\n```\n\n### Node.js-specific diagnostic decision trees\n\n**Segfault \u002F crash in native addon:**\n1. Is the crash reproducible with `node --napi-modules`? → Run `gdb`, capture `bt`\n2. Does `bt` point to a V8 handle scope issue? → Check `HandleScope` \u002F `EscapableHandleScope` usage in the addon\n3. Does it point to a libuv callback? → Inspect async handle lifetime and `uv_close()` sequencing\n4. No clear C++ frame? → Check for JS-side type mismatches passed into the native binding\n\n**V8 deoptimization \u002F performance regression:**\n1. Run `--trace-opt --trace-deopt` → identify the deoptimized function and reason (e.g., \"not a Smi\", \"wrong map\")\n2. Checkpoint: confirm the same function deoptimizes consistently across runs\n3. Inspect hidden class transitions (`--trace-ic`) and fix property addition order or type inconsistencies\n4. Re-run `--trace-opt` to confirm the function is now optimized\n\n**Build failure (node-gyp \u002F binding.gyp):**\n1. Is it a missing header? → Verify `include_dirs` in `binding.gyp` and Node.js header installation\n2. Is it a linker error? → Check `libraries` and `link_settings` entries; confirm ABI compatibility\n3. Is it platform-specific? → Consult `rules\u002Fbuild-system.md` for Windows\u002FmacOS\u002FLinux differences\n\nAlways consider both JavaScript-level and native-level causes, explain performance implications and trade-offs, and indicate the stability status of any experimental features discussed. Code examples should demonstrate Node.js internals patterns and be production-ready, accounting for edge cases typical developers might miss.\n","## When to use\n\nUse this skill when you need deep Node.js internals expertise, including:\n- C++ addon development\n- V8 engine debugging\n- libuv event loop issues\n- Build system problems\n- Compilation failures\n- Performance optimization at the engine level\n- Understanding Node.js core architecture\n- Writing or reviewing `nodejs\u002Fnode` commits and pull request descriptions\n\n## How to use\n\nRead individual rule files for detailed explanations and code examples:\n\n### V8 Engine\n\n- [rules\u002Fv8-garbage-collection.md](rules\u002Fv8-garbage-collection.md) - Scavenger, Mark-Sweep, Mark-Compact, generational GC\n- [rules\u002Fv8-hidden-classes.md](rules\u002Fv8-hidden-classes.md) - Hidden classes, inline caching, optimization\n- [rules\u002Fv8-jit-compilation.md](rules\u002Fv8-jit-compilation.md) - TurboFan, optimization\u002Fdeoptimization patterns\n\n### libuv\n\n- [rules\u002Flibuv-event-loop.md](rules\u002Flibuv-event-loop.md) - Event loop phases, timers, I\u002FO, idle, check, close\n- [rules\u002Flibuv-thread-pool.md](rules\u002Flibuv-thread-pool.md) - Thread pool size, blocking operations, UV_THREADPOOL_SIZE\n- [rules\u002Flibuv-async-io.md](rules\u002Flibuv-async-io.md) - Async I\u002FO patterns, handles, requests\n\n### Native Addons\n\n- [rules\u002Fnapi.md](rules\u002Fnapi.md) - N-API development, ABI stability, async workers\n- [rules\u002Fnode-addon-api.md](rules\u002Fnode-addon-api.md) - C++ wrapper patterns, best practices\n- [rules\u002Fnative-memory.md](rules\u002Fnative-memory.md) - Buffer handling, external memory, prevent leaks\n\n### Core Modules Internals\n\n- [rules\u002Fstreams-internals.md](rules\u002Fstreams-internals.md) - How Node.js streams work at C++ level\n- [rules\u002Fnet-internals.md](rules\u002Fnet-internals.md) - TCP\u002FUDP implementation, socket handling\n- [rules\u002Ffs-internals.md](rules\u002Ffs-internals.md) - libuv fs operations, sync vs async\n- [rules\u002Fcrypto-internals.md](rules\u002Fcrypto-internals.md) - OpenSSL integration, performance considerations\n- [rules\u002Fchild-process-internals.md](rules\u002Fchild-process-internals.md) - IPC, spawn, fork implementation\n- [rules\u002Fworker-threads-internals.md](rules\u002Fworker-threads-internals.md) - SharedArrayBuffer, Atomics, MessageChannel\n\n### JavaScript Internals\n\n- [rules\u002Fprimordials.md](rules\u002Fprimordials.md) - **Using primordials to prevent prototype pollution (required for `lib\u002Finternal\u002F`)**\n\n### Build & Contributing\n\n- [rules\u002Fbuild-and-test-workflow.md](rules\u002Fbuild-and-test-workflow.md) - **The edit-build-lint-test cycle (start here)**\n- [rules\u002Fpre-commit-lint.md](rules\u002Fpre-commit-lint.md) - **Mandatory lint, format, and `core-validate-commit` gate for every commit so CI passes first time**\n- [rules\u002Fconfigure.md](rules\u002Fconfigure.md) - `.\u002Fconfigure` flags for debug builds, ASan, Ninja, etc.\n- [rules\u002Fbuild-system.md](rules\u002Fbuild-system.md) - gyp, ninja, make, cross-platform compilation\n- [rules\u002Fcli-options.md](rules\u002Fcli-options.md) - Adding CLI options and gating experimental modules\n- [rules\u002Fcontributing.md](rules\u002Fcontributing.md) - How to contribute to Node.js core, the process\n- [rules\u002Fcommit-and-pr-guideline.md](rules\u002Fcommit-and-pr-guideline.md) - Commit message and PR description style, trailers, DCO sign-off, and validation\n- [rules\u002Freviewing-prs.md](rules\u002Freviewing-prs.md) - Reviewing PRs for correctness, clarity, and contribution quality\n\n### Documentation\n\n- [rules\u002Fdocumentation.md](rules\u002Fdocumentation.md) - **Updating doc\u002Fapi\u002F*.md files: structure, link ordering, error docs, code example constraints**\n\n### Debugging & Profiling\n\n- [rules\u002Fdebugging-native.md](rules\u002Fdebugging-native.md) - gdb, lldb, debugging C++ addons\n- [rules\u002Fprofiling-v8.md](rules\u002Fprofiling-v8.md) - --prof, --trace-opt, --trace-deopt, flame graphs\n- [rules\u002Fmemory-debugging.md](rules\u002Fmemory-debugging.md) - Heap snapshots, memory leak detection\n\n## Instructions\n\n### Node.js contribution writing\n\nWhen drafting a `nodejs\u002Fnode` commit or pull request, read\n[rules\u002Fcommit-and-pr-guideline.md](rules\u002Fcommit-and-pr-guideline.md).\nUse terse subsystem-prefixed titles and plain, matter-of-fact prose. Lead with\nconcrete behavior, explain the reason for the change, and omit hype, canned\nheadings, file-by-file narration, and unsupported claims. Include the\ncontributor's DCO sign-off, and never add `PR-URL:` or `Reviewed-By:` — those\nare added when the change lands. Validate the result with\n`npx core-validate-commit --no-validate-metadata \u003Csha>` in the `nodejs\u002Fnode`\ncheckout.\n\n### MANDATORY: Rebuild before testing\n\nNode.js embeds `lib\u002F` JavaScript files into the binary at compile time via\n`js2c`. **After ANY change to `src\u002F` or `lib\u002F`, you MUST rebuild before\nrunning tests.** Without a rebuild, tests run against stale code and results\nare meaningless.\n\n```\nedit src\u002F or lib\u002F  →  make -j$(nproc)  →  make lint  →  then test\n```\n\nNever skip the rebuild step. Never run `.\u002Fnode test\u002F...` after editing\nwithout building first.\n\nBefore starting work, **ask the user** about their build configuration\n(Make vs Ninja, debug vs release, what configure flags they use). Do not\nassume a specific setup. Most of the time, `.\u002Fconfigure` has already been\nrun and only `make -j$(nproc)` is needed to rebuild.\n\n### MANDATORY: Lint and format before every commit\n\nNode.js runs a `Linters` CI workflow on every non-draft pull request, and on\nUnix `make test` runs **no** linters. Run `make lint` before each `git\ncommit` — plus `make format-cpp` for C++ changes — so the lint jobs pass on\nthe first CI run instead of costing a force-push and another full cycle.\n\n```bash\nmake -j$(nproc)                                        # rebuild first\nmake lint                                              # JS, C++, MD, docs, YAML\n\n# C++ changes only — use the merge-base form, which is what CI checks:\nCLANG_FORMAT_START=\"$(git merge-base HEAD upstream\u002Fmain)\" make format-cpp\ngit --no-pager diff --exit-code                        # must be empty\n\ngit add -A && git commit -s                            # -s is mandatory\nnpx core-validate-commit --no-validate-metadata HEAD\n```\n\nNever skip a step because the change looks trivial, and never commit with\n\"will fix lint in a follow-up\".\n\n**Bare `make format-cpp` is not enough.** It defaults to\n`CLANG_FORMAT_START=HEAD` and formats only *staged* changes, while the\n`format-cpp` CI job formats everything from the merge base and fails on any\nresulting diff — so unformatted code committed earlier in the branch passes\nlocally and fails in CI. Always pass the merge-base form shown above.\n\n**Every commit must be created with `git commit -s`.** The `-s` flag adds the\n`Signed-off-by:` trailer certifying the Developer Certificate of Origin.\nWithout it the `signed-off-by` rule of `core-validate-commit` fails and the PR\ncannot land. The sign-off must be the human contributor's name and email —\nnever sign off with a tool or AI identity, and never fabricate someone else's.\nIf you forget it, amend with `git commit --amend --signoff`.\n\n`make lint` runs `lint-js`, `lint-cpp`, `lint-addon-docs`, `lint-md`, and\n`lint-yaml` — it does not cover every CI lint job. Python (`make lint-py`),\nshell (`tools\u002Flint-sh.mjs .`), C++ formatting, and commit-message validation\nare separate jobs. See [rules\u002Fpre-commit-lint.md](rules\u002Fpre-commit-lint.md)\nfor the full gate and the CI-job-to-command mapping.\n\nValidate every commit message with `core-validate-commit`, always with\n`--no-validate-metadata` — metadata validation is on by default and enforces\ntrailers that only exist after landing. **Never add `PR-URL:` or\n`Reviewed-By:` to a commit you author**; the landing process adds them.\n\nSee [rules\u002Fbuild-and-test-workflow.md](rules\u002Fbuild-and-test-workflow.md)\nfor the full workflow including configure flags, lint targets, and test\ncommands.\n\n### Core knowledge domains\n\nApply deep knowledge of Node.js internals across these domains:\n\n- **Core architecture**: Node.js core modules and their C++ implementations, V8 GC and JIT, libuv event loop mechanics, thread pool behavior, startup\u002Fmodule-loading lifecycle\n- **Native development**: N-API, node-addon-api, and NAN addon development; V8 C++ API handle management; memory safety; native debugging with gdb\u002Flldb\n- **Build systems**: node-gyp, gyp, ninja, make; cross-platform compilation; linker errors; dependency issues; platform-specific considerations (Windows, macOS, Linux, embedded)\n- **Performance & debugging**: Event loop profiling, memory leak detection in JS and native code, CPU flame graphs, V8 optimization\u002Fdeoptimization tracing\n\n### Quick-reference debugging commands\n\n**V8 optimization tracing:**\n```bash\nnode --trace-opt --trace-deopt script.js\n# Checkpoint: confirm no unexpected deoptimization warnings before proceeding to profiling\nnode --prof script.js && node --prof-process isolate-*.log > processed.txt\n```\n\n**Event loop lag detection:**\n```bash\nnode --trace-event-categories v8,node,node.async_hooks script.js\n```\n\n**Native addon debugging (gdb):**\n```bash\ngdb --args node --napi-modules .\u002Fbuild\u002FRelease\u002Faddon.node\n# Inside gdb:\nrun\nbt        # backtrace on crash\n# Checkpoint: verify backtrace shows the expected call site before applying a fix\n```\n\n**Heap snapshot for memory leaks:**\n```bash\nnode --inspect script.js   # then open chrome:\u002F\u002Finspect, take heap snapshot\n# Checkpoint: compare two consecutive heap snapshots to confirm leak growth before and after the fix; run valgrind --leak-check=full node addon_test.js to confirm no native leaks remain\n```\n\n### Node.js-specific diagnostic decision trees\n\n**Segfault \u002F crash in native addon:**\n1. Is the crash reproducible with `node --napi-modules`? → Run `gdb`, capture `bt`\n2. Does `bt` point to a V8 handle scope issue? → Check `HandleScope` \u002F `EscapableHandleScope` usage in the addon\n3. Does it point to a libuv callback? → Inspect async handle lifetime and `uv_close()` sequencing\n4. No clear C++ frame? → Check for JS-side type mismatches passed into the native binding\n\n**V8 deoptimization \u002F performance regression:**\n1. Run `--trace-opt --trace-deopt` → identify the deoptimized function and reason (e.g., \"not a Smi\", \"wrong map\")\n2. Checkpoint: confirm the same function deoptimizes consistently across runs\n3. Inspect hidden class transitions (`--trace-ic`) and fix property addition order or type inconsistencies\n4. Re-run `--trace-opt` to confirm the function is now optimized\n\n**Build failure (node-gyp \u002F binding.gyp):**\n1. Is it a missing header? → Verify `include_dirs` in `binding.gyp` and Node.js header installation\n2. Is it a linker error? → Check `libraries` and `link_settings` entries; confirm ABI compatibility\n3. Is it platform-specific? → Consult `rules\u002Fbuild-system.md` for Windows\u002FmacOS\u002FLinux differences\n\nAlways consider both JavaScript-level and native-level causes, explain performance implications and trade-offs, and indicate the stability status of any experimental features discussed. Code examples should demonstrate Node.js internals patterns and be production-ready, accounting for edge cases typical developers might miss.\n",{"metadata":24,"description":7},{"tags":25},"nodejs, nodejs-core, contributing, commit-message, pull-request, v8, libuv, cpp, native-addons, performance, debugging, internals","main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fnodejs-core",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill nodejs-core",{"tool":40,"command":41},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill nodejs-core",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill nodejs-core","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142,146,150,154,158,162],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"rules\u002Fbuild-and-test-workflow.md","REFERENCE","参考文档",13090,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fbuild-and-test-workflow.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"rules\u002Fbuild-system.md",7814,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fbuild-system.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"rules\u002Fchild-process-internals.md",12425,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fchild-process-internals.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"rules\u002Fcli-options.md",15188,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fcli-options.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"rules\u002Fcommit-and-pr-guideline.md",16615,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fcommit-and-pr-guideline.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"rules\u002Fconfigure.md",5199,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fconfigure.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"rules\u002Fcontributing.md",11323,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fcontributing.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"rules\u002Fcrypto-internals.md",11869,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fcrypto-internals.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"rules\u002Fdebugging-native.md",8040,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fdebugging-native.md",{"path":87,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":88,"sourceHtmlUrl":89},"rules\u002Fdocumentation.md",10813,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fdocumentation.md",{"path":91,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":92,"sourceHtmlUrl":93},"rules\u002Ffs-internals.md",10707,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Ffs-internals.md",{"path":95,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":96,"sourceHtmlUrl":97},"rules\u002Flibuv-async-io.md",10877,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Flibuv-async-io.md",{"path":99,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":100,"sourceHtmlUrl":101},"rules\u002Flibuv-event-loop.md",11329,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Flibuv-event-loop.md",{"path":103,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":104,"sourceHtmlUrl":105},"rules\u002Flibuv-thread-pool.md",10600,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Flibuv-thread-pool.md",{"path":107,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":108,"sourceHtmlUrl":109},"rules\u002Fmemory-debugging.md",12004,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fmemory-debugging.md",{"path":111,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":112,"sourceHtmlUrl":113},"rules\u002Fnapi.md",14348,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fnapi.md",{"path":115,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":116,"sourceHtmlUrl":117},"rules\u002Fnative-memory.md",12218,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fnative-memory.md",{"path":119,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":120,"sourceHtmlUrl":121},"rules\u002Fnet-internals.md",14085,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fnet-internals.md",{"path":123,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":124,"sourceHtmlUrl":125},"rules\u002Fnode-addon-api.md",14926,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fnode-addon-api.md",{"path":127,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":128,"sourceHtmlUrl":129},"rules\u002Fpre-commit-lint.md",11425,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fpre-commit-lint.md",{"path":131,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":132,"sourceHtmlUrl":133},"rules\u002Fprimordials.md",12900,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fprimordials.md",{"path":135,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":136,"sourceHtmlUrl":137},"rules\u002Fprofiling-v8.md",10085,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fprofiling-v8.md",{"path":139,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":140,"sourceHtmlUrl":141},"rules\u002Freviewing-prs.md",10586,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Freviewing-prs.md",{"path":143,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":144,"sourceHtmlUrl":145},"rules\u002Fstreams-internals.md",11993,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fstreams-internals.md",{"path":147,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":148,"sourceHtmlUrl":149},"rules\u002Fv8-garbage-collection.md",11131,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fv8-garbage-collection.md",{"path":151,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":152,"sourceHtmlUrl":153},"rules\u002Fv8-hidden-classes.md",9416,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fv8-hidden-classes.md",{"path":155,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":156,"sourceHtmlUrl":157},"rules\u002Fv8-jit-compilation.md",10416,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fv8-jit-compilation.md",{"path":159,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":160,"sourceHtmlUrl":161},"rules\u002Fworker-threads-internals.md",13639,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Frules\u002Fworker-threads-internals.md",{"path":163,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":164,"sourceHtmlUrl":165},"tile.json",355,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fnodejs-core\u002Ftile.json",[167,174,181,188,195,202],{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]