doc: create ai-guidelines and include to CONTRIBUTING by RafaelGSS · Pull Request #62105 · nodejs/node

RafaelGSS · 2026-03-04T21:24:24Z

As discussed in today's TSC meeting.

cc: @nodejs/tsc @BridgeAR

nodejs-github-bot · 2026-03-04T21:24:30Z

Review requested:

@nodejs/tsc

joyeecheung · 2026-03-05T11:56:14Z

There may be some ideas we can borrow from https://llvm.org/docs/AIToolPolicy.html - for example "good first issue" should not be picked up by AI is a good one.

RafaelGSS · 2026-03-05T14:04:23Z

There may be some ideas we can borrow from https://llvm.org/docs/AIToolPolicy.html - for example "good first issue" should not be picked up by AI is a good one.

I took inspiration from https://github.com/zulip/zulip/blob/main/CONTRIBUTING.md#ai-use-policy-and-guidelines

mcollina · 2026-03-05T15:59:17Z

+* **Verify accuracy** of any LLM-generated content before including it in a
+  PR description or comment.
+* **Complete pull request templates fully** rather than replacing them with
+  LLM-generated summaries.


Do we have a template? I thought those are for issues, not PRs.

Not strictly a template: https://github.com/nodejs/node/blob/main/.github/PULL_REQUEST_TEMPLATE.md?plain=1

It's not possible to fulfil the instructions "Complete pull request templates fully" based on the contents of https://github.com/nodejs/node/blob/main/.github/PULL_REQUEST_TEMPLATE.md?plain=1 so it looks like this sentence needs to be removed.

gurgunday

lgtm

indutny

I'd be against this contribution policy update. While many different opinions exist on the licensing terms of the code produced by LLMs, my opinion is that the generated code isn't explicitly licensed and attributed to the original authors so it cannot be considered open source regardless of the used prompt.

mcollina · 2026-03-17T17:44:59Z

+* **Verify accuracy** of any LLM-generated content before including it in a
+  PR description or comment.
+* **Complete pull request templates fully** rather than replacing them with
+  LLM-generated summaries.


Suggested change

* **Verify accuracy** of any LLM-generated content before including it in a

PR description or comment.

* **Complete pull request templates fully** rather than replacing them with

LLM-generated summaries.

* **Verify accuracy** of any LLM-generated content before including it in a

PR description or comment.

joyeecheung · 2026-03-17T17:50:33Z

In #61478 (comment) , regarding the usage of Claude Code, @mcollina suggested:

As it seems that you have a different position on this issue, I will bring this to the attention of the @nodejs/tsc for an official vote. On a side note, I would also officially summon the topic at the next OpenJS board meeting.

I added it to the TSC agenda tomorrow for awareness/context collection before moving to a proper vote. @indutny sorry about the short notice since this is just one day ahead of the meeting, but if you'd like to join the meeting to present your points please let us know.

mcollina

lgtm with a sentence removed

indutny · 2026-03-17T18:04:35Z

@joyeecheung thanks for considering me for this! I'd be happy to join if the time isn't in conflict with my work meetings tomorrow. Could you send me an invite, please?

mcollina · 2026-03-17T18:08:29Z

nodejs/TSC#1830 this is the issue. It might be reschedueld to the next meeting if there is low attedance given the timezone.

I think we can schedule the discussion for April 1st which will be in the morning PT so a lot of people can join, and I would table the vote for that session. I would try to get an answer from the Board by then.

bnb

After today's Summit discussion, I'd like to recommend that we adjust messaging to be "discouraged but allowed". I think that would generally represent the sentiment that was expressed and hit the median of the collaboratorship's opinion.

If people are chill with that, happy to submit prose suggestions.

tniessen · 2026-04-15T10:06:16Z

+acknowledged honestly (e.g., via an `Assisted-by:` tag in the commit
+metadata) so that reviewers have appropriate context.
+
+Pull requests that consist of AI-generated code the contributor has not


Suggested change

Pull requests that consist of AI-generated code the contributor has not

Pull requests that contain AI-generated code the contributor has not

tniessen · 2026-04-15T10:10:53Z

+every change they propose. Pull requests consisting of AI-generated code the
+contributor has not personally understood, tested, and verified will likely be closed
+without review.


Suggested change

every change they propose. Pull requests consisting of AI-generated code the

contributor has not personally understood, tested, and verified will likely be closed

without review.

every change they propose. Pull requests containing AI-generated code the

contributor has not personally understood, tested, and verified will likely be closed

without review.

tniessen · 2026-04-15T10:16:51Z

+* **Test thoroughly.** AI-generated code must pass the full test suite and
+  any manually written tests relevant to the change. Existing tests should not
+  be removed or modified without human verification. Do not rely on the LLM
+  to assess correctness.


Some hallucination machines may write tests based on the implementation of a feature instead of considering the expected behavior of the feature.

Suggested change

* **Test thoroughly.** AI-generated code must pass the full test suite and

any manually written tests relevant to the change. Existing tests should not

be removed or modified without human verification. Do not rely on the LLM

to assess correctness.

* **Test thoroughly.** AI-generated code must pass the full test suite and

any manually written tests relevant to the change. Existing tests should not

be removed or modified without human verification. Do not rely on the LLM

to assess correctness. It is crucial to manually verify the correctness of

tests against the expected behavior of the feature being tested,

independently of the feature's implementation.

Can we extract this and also apply to human-written code too? (but keep it here also)

I believe we have existing decade-old tests that should be subject to this

Mostly "increase coverage" PRs are highly subject to documenting bugs instead of fixing them (not just in Node.js, but overall)

JakobJingleheimer · 2026-04-18T17:29:39Z

The moderation policy would also need to be updated to align with this new policy doc (the moderation policy expressly forbids AI contributions from non-collaborators).

bmuenzenmeyer · 2026-04-20T01:31:55Z

The moderation policy would also need to be updated to align with this new policy doc (the moderation policy expressly forbids AI contributions from non-collaborators).

Opened nodejs/admin#1059

ChALkeR · 2026-04-20T12:01:44Z

+never be "I'm not sure. The AI did it."
+
+If AI tools assisted in generating a contribution, that should be
+acknowledged honestly (e.g., via an `Assisted-by:` tag in the commit


I would prefer for mostly-ai-driven (but reviewed by human) contributions to be explicitly labeled as mostly-ai-driven.

Assisted-by obscures that to an extent.

E.g. if the code is mostly auto-generated, it should be the main author and the human only a co-author and a Signed-off-by to signal acceptance/origin in terms of DCO.

Hm.

The OpenJSF policy (at https://openjsf.cdn.prismic.io/openjsf/aca4d5GXnQHGZDiZ_OpenJS_AI_Coding_Assistants_Policy.pdf) specifies Assisted-by for AI assistants indeed.

Still, non ideal, but likely not something that can be solved at a project level?

E.g. if the code is mostly auto-generated, it should be the main author and the human only a co-author and a Signed-off-by to signal acceptance/origin in terms of DCO.

I disagree with having tooling be the contribution's main author. This isn't aligned with taking responsibility for the contributions (signed-off-by !== author) and doesn't sit well with changelog entries.

While you may use assistants for the content it is ultimately you, the human, we expect a contribution from.

an option could be to also add a label

Co-Authored-By: Beth Griggs <bethanyngriggs@gmail.com>

Co-authored-by: Aditi <62544124+Aditi-1400@users.noreply.github.com> Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

Co-authored-by: Tobias Nießen <tniessen@tnie.de> Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com> Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> Co-authored-by: Efe <dogukankrskl@gmail.com>

joyeecheung

See #62105 (comment) - I think without applying my suggestion or something along the lines, the current wording encourages mentioning brand or trademark names in the commit message, in general I think this is inappropriate regardless it's about AI or not and turns this non-profit project into a marketing ground of vendors. If somehow there are non-profit agent/model names that are neither a brand nor a trademark, I think that's fine to include it int he commit message. But if they are brands/trademarks for profit, then -1 from me to put them in commit message metadata and they should belong to e.g. PR descriptions.

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

addressed

joyeecheung

LGTM % a suggestion to spell out exactly how the "approval of automated tooling" works

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

nodejs-github-bot added the doc Issues and PRs related to the documentations. label Mar 4, 2026

UlisesGascon approved these changes Mar 5, 2026

View reviewed changes

joyeecheung reviewed Mar 5, 2026

View reviewed changes

Comment thread doc/contributing/ai-guidelines.md Outdated

Aditi-1400 reviewed Mar 5, 2026

View reviewed changes

Comment thread doc/contributing/ai-guidelines.md Outdated

Renegade334 reviewed Mar 5, 2026

View reviewed changes

Comment thread doc/contributing/ai-guidelines.md Outdated

mcollina requested changes Mar 5, 2026

View reviewed changes

lpinca approved these changes Mar 5, 2026

View reviewed changes

Aditi-1400 approved these changes Mar 6, 2026

View reviewed changes

tniessen reviewed Mar 6, 2026

View reviewed changes

Comment thread doc/contributing/ai-guidelines.md Outdated

aduh95 reviewed Mar 9, 2026

View reviewed changes

Comment thread CONTRIBUTING.md Outdated

MikeMcC399 reviewed Mar 9, 2026

View reviewed changes

Comment thread doc/contributing/ai-guidelines.md Outdated

MikeMcC399 reviewed Mar 9, 2026

View reviewed changes

Comment thread CONTRIBUTING.md Outdated

This comment was marked as resolved.

Sign in to view

RafaelGSS requested a review from mcollina March 13, 2026 16:39

RafaelGSS added the commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. label Mar 13, 2026

gurgunday approved these changes Mar 13, 2026

View reviewed changes

RafaelGSS added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Mar 14, 2026

joyeecheung mentioned this pull request Mar 17, 2026

Virtual File System for Node.js #61478

Open

indutny suggested changes Mar 17, 2026

View reviewed changes

joyeecheung added the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label Mar 17, 2026

joyeecheung mentioned this pull request Mar 17, 2026

Node.js Technical Steering Committee (TSC) Meeting 2026-03-18 nodejs/TSC#1830

Open

mcollina reviewed Mar 17, 2026

View reviewed changes

mcollina approved these changes Mar 17, 2026

View reviewed changes

mcollina mentioned this pull request Mar 17, 2026

Vote on AI contributions nodejs/TSC#1831

Open

ovflowd mentioned this pull request Apr 11, 2026

Add AI_POLICY.md webpack/tsc#49

Closed

bnb reviewed Apr 14, 2026

View reviewed changes

tniessen reviewed Apr 15, 2026

View reviewed changes

openjs-meetings-bot Bot mentioned this pull request Apr 16, 2026

Node.js Technical Steering Committee (TSC) Meeting 2026-04-22 nodejs/TSC#1850

Open

bmuenzenmeyer mentioned this pull request Apr 20, 2026

Clarify moderation of LLM-generated content nodejs/admin#1059

Open

panva mentioned this pull request Apr 20, 2026

crypto: fix unsigned conversion of 4-byte RSA publicExponent #62839

Merged

ChALkeR reviewed Apr 20, 2026

View reviewed changes

openjs-meetings-bot Bot mentioned this pull request Apr 23, 2026

Node.js Technical Steering Committee (TSC) Meeting 2026-04-29 nodejs/TSC#1851

Open

openjs-meetings-bot Bot mentioned this pull request Apr 30, 2026

Node.js Technical Steering Committee (TSC) Meeting 2026-05-06 nodejs/TSC#1854

Open

RafaelGSS and others added 6 commits May 4, 2026 10:40

doc: create ai-guidelines and include to CONTRIBUTING

522a34e

Co-Authored-By: Beth Griggs <bethanyngriggs@gmail.com>

Apply suggestions from code review

2587c60

Co-authored-by: Aditi <62544124+Aditi-1400@users.noreply.github.com> Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

Apply suggestions from code review

5b63cb8

Co-authored-by: Tobias Nießen <tniessen@tnie.de> Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com> Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com> Co-authored-by: Efe <dogukankrskl@gmail.com>

fixup! Apply suggestions from code review

2243a91

fixup! fixup! Apply suggestions from code review

c935e3d

fixup! fixup! fixup! Apply suggestions from code review

2eeadf6

RafaelGSS force-pushed the add-ai-guidelines branch from c9e7c08 to 3fa6b77 Compare May 4, 2026 14:26

fixup! Apply suggestions from code review

7944826

RafaelGSS force-pushed the add-ai-guidelines branch from 3fa6b77 to 7944826 Compare May 4, 2026 14:26

jasnell approved these changes May 4, 2026

View reviewed changes

joyeecheung reviewed May 4, 2026

View reviewed changes

Comment thread doc/contributing/ai-guidelines.md Outdated

fixup! Apply suggestions from code review

d8668b6

joyeecheung previously requested changes May 4, 2026

View reviewed changes

fixup! fixup! Apply suggestions from code review

0c29829

joyeecheung reviewed May 5, 2026

View reviewed changes

Comment thread doc/contributing/ai-guidelines.md Outdated

Apply suggestions from code review

9d75ac0

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

joyeecheung approved these changes May 5, 2026

View reviewed changes

Comment thread doc/contributing/ai-guidelines.md Outdated

Update doc/contributing/ai-guidelines.md

68d04f4

Co-authored-by: Joyee Cheung <joyeec9h3@gmail.com>

	Pull requests that consist of AI-generated code the contributor has not
	Pull requests that contain AI-generated code the contributor has not

Uh oh!

Conversation

RafaelGSS commented Mar 4, 2026

Uh oh!

nodejs-github-bot commented Mar 4, 2026

Uh oh!

Uh oh!

joyeecheung commented Mar 5, 2026

Uh oh!

Uh oh!

RafaelGSS commented Mar 5, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This comment was marked as resolved.

Uh oh!

gurgunday left a comment

Choose a reason for hiding this comment

Uh oh!

indutny left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

joyeecheung commented Mar 17, 2026

Uh oh!

mcollina left a comment

Choose a reason for hiding this comment

Uh oh!

indutny commented Mar 17, 2026

Uh oh!

mcollina commented Mar 17, 2026

Uh oh!

bnb left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ChALkeR Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JakobJingleheimer commented Apr 18, 2026

Uh oh!

bmuenzenmeyer commented Apr 20, 2026

Uh oh!

ChALkeR Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

joyeecheung left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

indutny left a comment •

edited

Loading

bnb left a comment •

edited

Loading

ChALkeR Apr 20, 2026 •

edited

Loading

ChALkeR Apr 20, 2026 •

edited

Loading

joyeecheung left a comment •

edited

Loading