1. Habit
  2. Skills
  3. Node.js Core skill
mcollina · 2K installs

Node.js Core skill
Runs by itself, before each commit.

Commits that pass CI first.

Install the Node.js Core skill and make it a habit: follow https://gethabit.dev/skills/mcollina/nodejs-core.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

2K installs2K starsMIT licenceSource on GitHub ↗

Node.js Core

by mcollina · 2K installs

The skill

Node.js core is a skill for people who contribute to or debug nodejs/node: commit and PR style, the build-lint-test cycle, native addon crashes, V8 deoptimizations, node-gyp builds and libuv issues.

Only when you ask.

The habit

Commits that pass CI first.

↻ Runs by itselfbefore each commit

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

before each commit. Runs in Claude Code.

  • ↻ before each commit
  • event: change to src/ or lib/ ready to commit

02

It checks its work

lint and commit validation. If a check fails, it tries again.

  • ✓make -j$(nproc) builds
  • ✓make lint passes
  • ✓git --no-pager diff --exit-code is empty after make format-cpp
  • ✓npx core-validate-commit --no-validate-metadata HEAD passes

03

It remembers

build setup notes. The next run reads it first: your build configuration: Make or Ninja, debug or release, configure flags.

loops/nodejs-core-commit-loop/notes.md

One run, step by step.
Then it stops.

Stop ruleStops after one commit or two failed retries.

  1. 01

    Ask build setup

    Ask the user about Make or Ninja, debug or release and configure flags, unless the notes already hold them.

  2. 02

    Rebuild

    Run make -j$(nproc) after any change to src/ or lib/ before testing.

  3. 03

    Lint

    Run make lint, and for C++ changes run make format-cpp with CLANG_FORMAT_START set to the merge base.

  4. 04

    Check the diff

    Run git --no-pager diff --exit-code and require it to be empty.

  5. 05

    Commit signed

    Commit with git commit -s using the human contributor's sign-off and a terse subsystem-prefixed title.

  6. 06

    Validate message

    Run npx core-validate-commit --no-validate-metadata HEAD and never add PR-URL or Reviewed-By.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Node.js Core skill helps.

Use it when

  • ✓ You commit to nodejs/node
  • ✓ A native addon segfaults
  • ✓ A function deoptimizes in V8

Skip it when

  • – You write normal app code in Node.js
  • – You only need JavaScript help

Questions

Node.js Core skill, answered.

Why rebuild before tests?

Node.js embeds lib/ files into the binary at compile time, so tests without a rebuild run old code.

Is bare make format-cpp enough?

No. The skill says to pass the merge-base form, because CI formats from the merge base.

How do I install the Node.js Core skill?

Copy the prompt at the top into your agent. It installs the skill from mcollina/skills and sets up the habit. Or run npx skills add mcollina/skills --skill nodejs-core.

Is the Node.js Core skill free?

Yes. It is published under MIT. Habit is free too.

Node.js Core. Now as a habit.

Install the Node.js Core skill and make it a habit: follow https://gethabit.dev/skills/mcollina/nodejs-core.md

  • Free
  • No account
  • Undo in one line

All mcollina skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by mcollina, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.