doc: refactor the AI guidelines - #65269
Open
joyeecheung wants to merge 2 commits into
Open
Conversation
The earlier version of the document contains duplications and has become logically disconnected after iteration. This patch wordsmiths it a bit to make it more coherent: - Merge policy points that have been repeated in the guidelines into the opening policy. - Remove redundant taglines. - Reword the paragraphs so that they appear more logical: -> decision making and accountability is human-only -> AI assistance is not prohibited -> disclosure and licensing -> verification and review requirement -> other off limits items (automation, good first issues) - Reword the guidelines to contextualize the suggestions with the use of AI instead of being generic. - Change the tone of the document to be more in line with other documents we have (e.g. avoid being too imperative or calling out "you" constantly) Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
Collaborator
|
Review requested:
|
legendecas
reviewed
Aug 13, 2026
joyeecheung
force-pushed
the
consolidate-ai-guidelines
branch
from
August 13, 2026 22:16
4b185d4 to
4783c93
Compare
mcollina
reviewed
Aug 15, 2026
| every change they propose. The answer to "Why is X an improvement?" can | ||
| never be "I'm not sure. The AI did it." | ||
| The Node.js project does not prohibit the use of AI tools in contributions, but | ||
| when the contribution is generated with AI, the contributor must disclose the use |
Member
There was a problem hiding this comment.
Suggested change
| when the contribution is generated with AI, the contributor must disclose the use | |
| when the contribution is generated with AI, the contributor should disclose the use |
I would be more comfortable with a should here.
| The Node.js project does not prohibit the use of AI tools in contributions, but | ||
| when the contribution is generated with AI, the contributor must disclose the use | ||
| of such tools, and the extent to which the contributor has personally verified | ||
| the generated output. The changes submitted to the Node.js code base must still satisfy |
Member
There was a problem hiding this comment.
The paragraph above states that one takes full responsibility of what they send. A consequence of that statement is that one has to verify the generated output. They should not state they do, they have to do it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The earlier version of the document contains duplications and has become logically disconnected after iteration. This patch wordsmiths it a bit to make it more coherent:
-> decision making and responsibility is human-only
-> AI assistance is not prohibited
-> disclosure and licensing
-> verification and review requirement
-> other off limits items (automation, good first issues)