Auto-generated tile from GitHub (10 skills)
92
94%
Does it follow best practices?
Impact
92%
1.16xAverage score across 44 eval scenarios
Advisory
Suggest reviewing before use
Use the Node.js commit style for changes affecting Node.js core or Node.js-core-like repositories.
subsystem: short imperative description
Longer explanation of the change if needed.
Fixes: https://github.com/nodejs/node/issues/12345
Refs: https://github.com/nodejs/node/pull/12344Examples of subsystem prefixes:
fs:stream:http:crypto:test:doc:build:Use core-validate-commit to check commit message format:
# Validate last commit message
git log -1 --pretty=%B | npx core-validate-commit
# Validate a message draft
printf "fs: fix race in readdir\n\nFixes: https://github.com/nodejs/node/issues/12345\n" | npx core-validate-commitIf validation fails, amend the commit message and re-run validation.
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 ChatGPTevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
skills
documentation
fastify
init
linting-neostandard-eslint9
node
nodejs-core
rules
oauth
octocat
snipgrapher