linux-kernel - Re: [RFC 1/2] AI: Add unified AI coding assistant configuration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87wm7w5dnd.fsf@trenco.lwn.net>
Date: Fri, 25 Jul 2025 12:27:50 -0600
From: Jonathan Corbet <corbet@....net>
To: Sasha Levin <sashal@...nel.org>, workflows@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: rostedt@...dmis.org, kees@...nel.org, konstantin@...uxfoundation.org,
 josh@...htriplett.org, Sasha Levin <sashal@...nel.org>
Subject: Re: [RFC 1/2] AI: Add unified AI coding assistant configuration

Sasha Levin <sashal@...nel.org> writes:

> Create a single source of truth for AI instructions in
> Documentation/AI/main.md with symlinks for all major AI coding
> assistants:
> - CLAUDE.md (Claude Code)
> - .github/copilot-instructions.md (GitHub Copilot)
> - .cursorrules (Cursor)
> - .codeium/instructions.md (Codeium)
> - .continue/context.md (Continue)
> - .windsurfrules (Windsurf)
> - Documentation/AIder.conf.yml (Aider)
>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
> ---
>  .aider.conf.yml                 | 1 +
>  .codeium/instructions.md        | 1 +
>  .continue/context.md            | 1 +
>  .cursorrules                    | 1 +
>  .github/copilot-instructions.md | 1 +
>  .windsurfrules                  | 1 +
>  CLAUDE.md                       | 1 +
>  Documentation/AI/main.md        | 5 +++++

So I'm gonna ignore (for now) the substantive issues here to ask: do we
*really* need to introduce Markdown into Documentation/?  Are these
things really unable to understand RST?  Why not add a file that can be
part of the docs build so people can see the instructions that are being
provided?

Thanks,

jon