nodejs-core
Contributes to and debugs Node.js core, including nodejs/node 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/node, or diagnosing C++ addons, binding.gyp failures, segfaults, native leaks, V8 deoptimizations, and event-loop internals.
Security Assessment
About nodejs-core
Node.js Core is a deep-internals expertise skill for contributing to and debugging Node.js core itself. It solves the problem that working in nodejs/node requires knowledge spanning C++ addons, the V8 engine, libuv, the build system, and the project's contribution conventions - knowledge that is scattered and hard to apply consistently. The skill packages this into a SKILL.md index plus a large set of focused rule files that the assistant reads on demand.
Its rule library covers V8 (garbage collection, hidden classes and inline caching, TurboFan JIT and deopt patterns), libuv (event-loop phases, thread pool and UV_THREADPOOL_SIZE, async I/O), native addons (N-API/node-addon-api, native memory and leak prevention), core-module internals (streams, net, fs, crypto, child_process, worker threads), and JavaScript internals like primordials for preventing prototype pollution in lib/internal. It also documents the build-and-test cycle, mandatory pre-commit lint and core-validate-commit gate, ./configure flags for debug/ASan/Ninja builds, commit-message and PR-description style with DCO sign-off, PR reviewing, documentation editing, and native debugging and profiling with gdb/lldb, --prof, --trace-opt/--trace-deopt, and heap snapshots.
It targets Node.js core contributors, native-addon authors, and engineers diagnosing native crashes, segfaults, memory leaks, V8 deoptimizations, node-gyp/binding.gyp build failures, and event-loop issues. Typical use cases include drafting or reviewing a nodejs/node commit or PR, understanding core architecture, and debugging or optimizing at the engine level. The code shown in rule files (for example child_process spawn/fork/IPC and file-descriptor passing) is illustrative internals documentation for education, not an executable tool.
FAQ
Who is this skill for?
Node.js core contributors and engineers doing deep internals work: C++ addon development, V8 debugging, libuv event-loop issues, build/compilation failures, and engine-level performance optimization, as well as anyone drafting or reviewing nodejs/node commits and PRs.
How is the content organized?
As a SKILL.md index pointing to focused rule files under rules/, grouped into V8, libuv, native addons, core-module internals, JavaScript internals, build/contributing, documentation, and debugging/profiling. You read the relevant rule file for detail and code examples.
Does it help with the contribution process itself?
Yes. It documents the edit-build-lint-test cycle, the mandatory pre-commit lint/format and core-validate-commit gate, ./configure flags, commit and PR guidelines with DCO sign-off, and how to review PRs and update doc/api markdown.
Does it run or build anything itself?
No. It is a reference skill; the code samples (such as spawn/fork/IPC internals) illustrate how Node.js works internally and are not an executable tool.
What debugging and profiling topics are covered?
Native debugging with gdb and lldb for C++ addons, V8 profiling with --prof, --trace-opt, and --trace-deopt plus flame graphs, and memory debugging via heap snapshots and leak detection.
All Files
30 filesInstall nodejs-core
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
mcollina/skills