docs: Add AI Usage Policy (#20510)

nzakas · snitin315 · web-flow · commit a0d1a3772679 · 2026-03-07T16:55:57.000+09:00
* docs: Add AI Usage Policy

* Update CONTRIBUTING.md

* Remove extra content

* Revert changes to code conventions

* Update docs/src/contribute/ai-policy.md

Co-authored-by: Nitin Kumar &lt;snitin315@gmail.com&gt;

* Apply feedback

* Update docs/src/contribute/ai-policy.md

Co-authored-by: Nitin Kumar &lt;snitin315@gmail.com&gt;

* Update policy

---------

Co-authored-by: Nitin Kumar &lt;snitin315@gmail.com&gt;
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -6,6 +6,10 @@ Please be sure to read the contribution guidelines before making or requesting a
 
 This project adheres to the [OpenJS Foundation Code of Conduct](https://eslint.org/conduct). We kindly request that you read over our code of conduct before contributing.
 
+## AI Usage Policy
+
+ESLint welcomes contributions from everyone, including those created with the assistance of Artificial Intelligence (AI) tools. We ask that you adhere to the [AI Usage Policy](https://eslint.org/docs/latest/contribute/ai-policy) when submitting contributions created with the assistance of AI tools.
+
 ## Filing Issues
 
 Before filing an issue, please be sure to read the guidelines for what you're reporting:
diff --git a/docs/src/contribute/ai-policy.md b/docs/src/contribute/ai-policy.md
@@ -0,0 +1,39 @@
+---
+title: AI Usage Policy
+eleventyNavigation:
+    key: ai policy
+    parent: contribute to eslint
+    title: AI Usage Policy
+    order: 1
+---
+
+ESLint welcomes contributions from everyone, including those created with the assistance of Artificial Intelligence (AI) tools. We believe AI can be a powerful tool for improving software and want to encourage its responsible use in our project.
+
+To ensure that AI contributions are integrated smoothly and maintain the quality of the codebase, we have established the following guidelines:
+
+## Disclosure
+
+If you use AI to generate an issue or a pull request, you must clearly disclose this in your submission. This helps maintainers understand the context of the contribution and perform appropriate reviews.
+
+Issues and pull requests that do not disclose the use of AI may be closed without review. Those who violate this policy repeatedly may be blocked from contributing to ESLint.
+
+## Human Responsibility
+
+While AI can assist in generating code or text, the ultimate responsibility for the contribution remains with the human submitter.
+
+- **Review your work:** Before submitting a pull request generated by AI, you are expected to have thoroughly reviewed and tested the code yourself. Ensure it meets ESLint's coding standards and correctly addresses the issue.
+- **Human responses:** When maintainers provide feedback or ask questions on your submission, we expect a human to respond. Please do not feed maintainer comments back into an AI to generate responses. We value human interaction and technical discussion.
+- **Edit for readability:** AI-generated content must be edited to make it easy for maintainers to review. This includes trimming unnecessary content, improving formatting, and ensuring that the contribution is clear and concise. PRs and issues that are difficult to review due to AI-generated content may be closed without review.
+
+## Pull Request Acceptance Criteria
+
+To help manage the volume of contributions, we have a specific policy for AI-generated pull requests:
+
+- **Accepted Issues Only:** AI-generated PRs will only be considered for issues that have been officially marked as `accepted` by the ESLint team.
+- **Otherwise Closed:** AI-generated PRs submitted for issues that have not been marked as `accepted` will be closed without review.
+
+We appreciate your cooperation in following these guidelines as we explore the benefits of AI-assisted development together!
+
+## Compensation
+
+ESLint does not provide compensation, either to team members or through the contributor pool, for contributions created primarily by AI. This is because we want to encourage human creativity and effort in our project, and we believe that AI should be used as a tool to assist rather than replace human contributions.
diff --git a/docs/src/contribute/architecture/index.md b/docs/src/contribute/architecture/index.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: architecture
     parent: contribute to eslint
     title: Architecture
-    order: 5
+    order: 6
 ---
 
 :::img-container
diff --git a/docs/src/contribute/core-rules.md b/docs/src/contribute/core-rules.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: contribute core rule
     parent: contribute to eslint
     title: Contribute to Core Rules
-    order: 11
+    order: 12
 ---
 
 The ESLint core rules are the rules included in the ESLint package.
diff --git a/docs/src/contribute/development-environment.md b/docs/src/contribute/development-environment.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: development environment
     parent: contribute to eslint
     title: Set up a Development Environment
-    order: 6
+    order: 7
 ---
 
 {%- from 'components/npm_tabs.macro.html' import npm_tabs with context %}
diff --git a/docs/src/contribute/governance.md b/docs/src/contribute/governance.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: governance
     parent: contribute to eslint
     title: Governance
-    order: 12
+    order: 13
 ---
 
 ESLint is an open source project that depends on contributions from the community. Anyone may contribute to the project at any time by submitting code, participating in discussions, making suggestions, or any other contribution they see fit. This document describes how various types of contributors work within the ESLint project.
diff --git a/docs/src/contribute/index.md b/docs/src/contribute/index.md
@@ -14,6 +14,10 @@ This guide is intended for anyone who wants to contribute to an ESLint project.
 
 ESLint welcomes contributions from everyone and adheres to the [OpenJS Foundation Code of Conduct](https://eslint.org/conduct). We kindly request that you read over our code of conduct before contributing.
 
+## [AI Usage Policy](ai-policy)
+
+We welcome AI-assisted contributions as long as they follow our guidelines for disclosure and human review.
+
 ## [Report Bugs](report-bugs)
 
 Think you found a problem? We'd love to hear about it. This section explains how to submit a bug, the type of information we need to properly verify it, and the overall process.
diff --git a/docs/src/contribute/package-json-conventions.md b/docs/src/contribute/package-json-conventions.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: package.json conventions
     parent: contribute to eslint
     title: Package.json Conventions
-    order: 8
+    order: 9
 ---
 
 The following applies to the "scripts" section of `package.json` files.
diff --git a/docs/src/contribute/propose-new-rule.md b/docs/src/contribute/propose-new-rule.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: propose rule
     parent: contribute to eslint
     title: Propose a New Rule
-    order: 2
+    order: 3
 ---
 
 ESLint is all about rules. For most of the project's lifetime, we've had over 200 rules, and that list continues to grow. However, we can't just accept any proposed rule because all rules need to work cohesively together. As such, we have some guidelines around which rules can be part of the ESLint core and which are better off as custom rules and plugins.
diff --git a/docs/src/contribute/propose-rule-change.md b/docs/src/contribute/propose-rule-change.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: propose rule change
     parent: contribute to eslint
     title: Propose a Rule Change
-    order: 3
+    order: 4
 ---
 
 Occasionally, a core ESLint rule needs to be changed. This is not necessarily a bug, but rather, an enhancement that makes a rule more configurable. In those situations, we will consider making changes to rules.
diff --git a/docs/src/contribute/pull-requests.md b/docs/src/contribute/pull-requests.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: submit pull request
     parent: contribute to eslint
     title: Submit a Pull Request
-    order: 10
+    order: 11
 ---
 
 If you want to contribute to an ESLint repo, please use a GitHub pull request. This is the fastest way for us to evaluate your code and to merge it into the code base. Please don't file an issue with snippets of code. Doing so means that we need to manually merge the changes in and update any appropriate tests. That decreases the likelihood that your code is going to get included in a timely manner. Please use pull requests.
diff --git a/docs/src/contribute/report-bugs.md b/docs/src/contribute/report-bugs.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: report bugs
     parent: contribute to eslint
     title: Report Bugs
-    order: 1
+    order: 2
 ---
 
 If you think you've found a bug in ESLint, please [create a new issue](https://github.com/eslint/eslint/issues/new/choose) or a [pull request](pull-requests) on GitHub.
diff --git a/docs/src/contribute/report-security-vulnerability.md b/docs/src/contribute/report-security-vulnerability.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: report security vulnerability
     parent: contribute to eslint
     title: Report a Security Vulnerability
-    order: 13
+    order: 14
 ---
 
 To report a security vulnerability in ESLint, please use our [create an advisory form](https://github.com/eslint/eslint/security/advisories/new) on GitHub.
diff --git a/docs/src/contribute/request-change.md b/docs/src/contribute/request-change.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: request change
     parent: contribute to eslint
     title: Request a Change
-    order: 4
+    order: 5
 ---
 
 If you'd like to request a change to ESLint, please [create a new issue](https://github.com/eslint/eslint/issues/new/choose) on GitHub. Be sure to include the following information:
diff --git a/docs/src/contribute/tests.md b/docs/src/contribute/tests.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: run tests
     parent: contribute to eslint
     title: Run the Tests
-    order: 7
+    order: 8
 ---
 
 Most parts of ESLint have unit tests associated with them. Unit tests are written using [Mocha](https://mochajs.org/) and are required when making contributions to ESLint. You'll find all of the unit tests in the `tests` directory.
diff --git a/docs/src/contribute/work-on-issue.md b/docs/src/contribute/work-on-issue.md
@@ -4,7 +4,7 @@ eleventyNavigation:
     key: work on issues
     parent: contribute to eslint
     title: Work on Issues
-    order: 9
+    order: 10
 ---
 
 Our public [issues tracker](https://github.com/eslint/eslint/issues) lists all of the things we plan on doing as well as suggestions from the community. Before starting to work on an issue, be sure you read through the rest of this page.
