Add a policy on AI-generated / AI-assisted contributions

Open Beginner friendly

#6,396 opened on Jul 27, 2026 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 65/100

Issue type: Documentation
Clarity: Mostly clear
Activity status: Quiet
Domain: documentation

Research direction

Read CONTRIBUTING.md and the existing attribution guidance in .github/instructions/specs.instructions.md first. Add the requested AI-assisted contribution policy to CONTRIBUTING.md, aligning its terminology with the existing guidance and PR-template disclosure. Done means the acceptance criterion is met and the wording has received the required team review, with CELA consultation if appropriate.

Written by the indexing model from the issue text.

Description

Issue-Feature

Part of #6393.

Problem

Nothing in CONTRIBUTING.md or the pull request template addresses AI-generated or AI-assisted contributions. As we label more issues Help-Wanted, we want to welcome responsible AI-assisted work while guarding against low-effort, unreviewed AI-generated PRs.

Proposed change

Add a section to CONTRIBUTING.md covering:

Contributors are fully accountable for AI-assisted code as if they wrote it themselves - they must understand it, and it must meet the same conventions, testing, and evidence bar as any other contribution.
Material use of AI generation should be disclosed in the PR.
Low-effort, unreviewed, or unverifiable AI-generated PRs may be closed.

Align terminology with the existing spec attribution guidance in .github/instructions/specs.instructions.md, which already documents crediting AI assistance in the spec author field.

Notes for engineers / review

The wording should be reviewed by the team (and, if appropriate, CELA) before merging. This issue creates the draft and the placement; final language needs sign-off.

Acceptance criteria

CONTRIBUTING.md includes an AI-assisted contribution policy consistent with the PR template disclosure (see the PR-template sub-issue).

(Created with GitHub Copilot assistance.)

Dominant language: C++
Stars: 26.4k
Forks: 1.8k
Avg merge: 1d 14h
Merged PRs (30d): 13

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] NULL pointer dereference in llm_running_callback (NGZA-AX-LLM #3) Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

AXERA-TECH/ax-llm#77 · Opened Sep 22, 2026
resume() sends a second HTTP response (400) after a successful resume Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

games-on-whales/wolf#509 · Opened Sep 21, 2026
pn7160: reader goes permanently deaf — post-read IRQ-low check fails reads that succeeded Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

esphome/esphome#19452 · Opened Sep 21, 2026
Eval bug: Ministral-3 tool-calls during reasoning are not processed Open

bug-unconfirmed

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

ggml-org/llama.cpp#29248 · Opened Sep 21, 2026
run_tests.py fails on windows, but running tests individually works Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

NVIDIA/cuda-samples#453 · Opened Sep 21, 2026

More C++ issues