mcollina/nodejs-core

Debugs native module crashes, optimizes V8 performance, configures node-gyp builds, writes N-API/node-addon-api bindings, and diagnoses libuv event loop issues in Node.js. Use when working with C++ addons, native modules, binding.gyp, node-gyp errors, segfaults, memory leaks in native code, V8 optimization/deoptimization, libuv thread pool tuning, N-API or NAN bindings, build system failures, or any Node.js internals below the JavaScript layer.

Quality

99%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

name:: commit-messages
description:: Node.js-style commit message formatting and validation
metadata:: {"tags":"commit-message, git, contributing, nodejs-core"}

Commit Message Formatting

Name: mcollina/nodejs-core
Rating: 99 (1 reviews)
Author: mcollina

Use the Node.js commit style for changes affecting Node.js core or Node.js-core-like repositories.

Required format

subsystem: short imperative description

Longer explanation of the change if needed.

[optional footers]

Use canonical Node.js-style prefixes such as:

fs:
stream:
http:
crypto:
test:
doc:
build:

Footer rules (`Fixes:` vs `Refs:`)

Use footer lines deliberately — they are not interchangeable.

Use Fixes: <issue-url> when the commit should close an issue.
Use Refs: <issue-or-pr-url> when linking related work that is not closed by this commit.
Use both when both semantics apply.
If no tracker link is relevant, omit both footers.

When a task explicitly asks for a Refs: footer, include the Refs: line exactly and do not omit it.

Valid footer examples

Fixes only

fs: avoid double-close race in FileHandle

Guard close path to make repeated close idempotent.

Fixes: https://github.com/nodejs/node/issues/12345

Refs only

stream: align docs for Readable.from backpressure

Clarify behavior and edge-case notes without closing the tracking issue.

Refs: https://github.com/nodejs/node/issues/23456

Both Fixes and Refs

http: normalize header casing in parser fast path

Apply casing normalization and add regression coverage.

Fixes: https://github.com/nodejs/node/issues/34567
Refs: https://github.com/nodejs/node/pull/34566

Validate before pushing

Use core-validate-commit to check commit message format:

Package: https://www.npmjs.com/package/core-validate-commit

# Validate last commit message
git log -1 --pretty=%B | npx core-validate-commit

# Validate a Fixes-only draft
printf "fs: fix race in readdir\n\nFixes: https://github.com/nodejs/node/issues/12345\n" | npx core-validate-commit

# Validate a Refs-only draft
printf "doc: clarify event loop phase wording\n\nRefs: https://github.com/nodejs/node/pull/12344\n" | npx core-validate-commit

If validation fails, amend the commit message and re-run validation.

Prohibited signatures and attribution

Do not add AI/agent signatures or co-authorship lines under any circumstance.

Examples that must never be added:

Co-Authored-By: Claude ...
Co-Authored-By: Codex ...
Generated by ChatGPT
Any "Signed-off-by" or footer claiming the agent as an author