# LLVM forbids AI tools on issues labelled "good first issue", keeping them as learning opportunities for new contributors

Page: https://flyvolo.ai/en/changes/ev-20260116-experienced-software-engineer-6
Date: 2026-01-16 · Stage: Constraint
Can this record move a task judgement? yes
Occupation: https://flyvolo.ai/en/careers/experienced-software-engineer

## Scope

One large open-source compiler project, binding on its contributors. The policy says AI tools must not be used to fix GitHub issues labelled good first issue, because those issues are generally not urgent and are intended to be learning opportunities for new contributors; it says passing maintainer feedback to an LLM does not help anyone grow, and that reviewing changes from new contributors is part of growing the next generation of contributors. The clause came in with the policy's first version, committed on 16 January 2026; later edits did not change it. It is one project's rule, not an employer's.

## Source

- LLVM Project — LLVM AI Tool Use Policy (llvm/docs/AIToolPolicy.md; added 16 January 2026) — https://llvm.org/docs/AIToolPolicy.html (primary source)

## What this means

At least one major engineering community has written down that some work is kept for people to learn on, and that reviewing a newcomer's change is how the next experienced engineers are made.

## What it does not show yet

One open-source project's rule; it says nothing about mentoring inside companies, or whether the newcomers it reserves work for keep arriving.

## How to verify it yourself

Open the LLVM AI Tool Use Policy on llvm.org and find "intended to be learning opportunities for new contributors".


More: https://flyvolo.ai/llms.txt