From cba03ea94aeebf8144205c45c958bb70d34ce88e Mon Sep 17 00:00:00 2001 From: Jesse Beder Date: Sat, 10 Oct 2026 12:10:27 -0500 Subject: [PATCH 1/2] Prohibit AI-generated commit messages --- CONTRIBUTING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2031bdbe0..8a53b2d2f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -41,4 +41,5 @@ The following rules are in service of producing correct, maintainable code while 1. You (the author of the PR) are responsible for the PR, regardless of the tools you use to create it. Make sure you understand it thoroughly and agree with its contents before you submit a PR. 2. Corollary: AI is not a co-author, AI is a tool. If you wouldn't list Emacs as a co-author, don't list Claude either. (Maybe it will be someday, but not yet.) 3. Do not use AI to generate documentation. It's fine for code, but it's [painful](https://samkriss.substack.com/p/if-you-let-ai-do-your-writing-i-will) to read AI text. -4. No "low effort" AI PRs. Don't just paste an issue into Claude and ask it to fix it; don't just ask it for a vulnerability report. That's fine as a starting point, but if that's *all* you do, then you haven't provided any value; you've just added work for the maintainers, who could have easily pasted the issue into Claude themselves. +4. Corollary: Write your own commit descriptions; do NOT use AI to generate it. Commit descriptions are key to understand the point of a change, and AIs are very bad at this. They litter the message with garbage like "4931/4931 tests pass" and rarely explain the purpose well. (Maybe it will someday, but not yet.) It's OK for the entire code change to be AI-generated (pending you stand behind it, per the other rules), but NOT the commit message. +5. No "low effort" AI PRs. Don't just paste an issue into Claude and ask it to fix it; don't just ask it for a vulnerability report. That's fine as a starting point, but if that's *all* you do, then you haven't provided any value; you've just added work for the maintainers, who could have easily pasted the issue into Claude themselves. From 81cd3173de44bc67a319cbbc7999e321167eb56a Mon Sep 17 00:00:00 2001 From: Jesse Beder Date: Sun, 11 Oct 2026 10:11:53 -0500 Subject: [PATCH 2/2] Minor wording tweaks. --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8a53b2d2f..4d8b6e5a1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -41,5 +41,5 @@ The following rules are in service of producing correct, maintainable code while 1. You (the author of the PR) are responsible for the PR, regardless of the tools you use to create it. Make sure you understand it thoroughly and agree with its contents before you submit a PR. 2. Corollary: AI is not a co-author, AI is a tool. If you wouldn't list Emacs as a co-author, don't list Claude either. (Maybe it will be someday, but not yet.) 3. Do not use AI to generate documentation. It's fine for code, but it's [painful](https://samkriss.substack.com/p/if-you-let-ai-do-your-writing-i-will) to read AI text. -4. Corollary: Write your own commit descriptions; do NOT use AI to generate it. Commit descriptions are key to understand the point of a change, and AIs are very bad at this. They litter the message with garbage like "4931/4931 tests pass" and rarely explain the purpose well. (Maybe it will someday, but not yet.) It's OK for the entire code change to be AI-generated (pending you stand behind it, per the other rules), but NOT the commit message. +4. Corollary: Write your own PR and commit messages; do NOT use AI to generate them. These descriptions are key to understand the point of a change, and AIs are very bad at them. They litter the message with garbage like "4931/4931 tests pass" and rarely explain the purpose well. (Maybe it will someday, but not yet.) It's OK for the entire code change to be AI-generated (pending you stand behind it, per the other rules), but NOT the commit message. 5. No "low effort" AI PRs. Don't just paste an issue into Claude and ask it to fix it; don't just ask it for a vulnerability report. That's fine as a starting point, but if that's *all* you do, then you haven't provided any value; you've just added work for the maintainers, who could have easily pasted the issue into Claude themselves.