From: Sasha Levin <sashal@kernel.org>
To: sashal@kernel.org
Cc: corbet@lwn.net, josh@joshtriplett.org, kees@kernel.org,
konstantin@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
workflows@vger.kernel.org
Subject: [PATCH v2 0/2] Add unified configuration for coding agents
Date: Sat, 9 Aug 2025 19:40:06 -0400 [thread overview]
Message-ID: <20250809234008.1540324-1-sashal@kernel.org> (raw)
This patch series adds unified configuration and documentation for coding
agents working with the Linux kernel codebase. As coding agents become
increasingly common in software development, it's important to establish
clear guidelines for their use in kernel development.
The series consists of two patches:
1. README: restructure with role-based documentation and guidelines
- Reorganizes README to provide targeted documentation paths for
different user roles (developers, researchers, security experts,
maintainers, and AI coding assistants)
- Adds quick start section and essential documentation links
- Establishes proper attribution requirements for AI-assisted
contributions using Assisted-by tags with agent details
2. agents: add unified agent coding assistant configuration
- Creates configuration files for major coding agents (Claude,
GitHub Copilot, Cursor, Codeium, Continue, Windsurf, and Gemini)
- Uses @README references to point all agents to the central
documentation, ensuring consistency across tools
The agent configuration files now use @README references instead of
symlinks.
Example agent attribution in commits:
Assisted-by: Claude-claude-3-opus-20240229 checkpatch
This ensures full transparency about agent involvement in code development
while maintaining proper attribution standards.
Sasha Levin (2):
README: restructure with role-based documentation and guidelines
agents: add unified agent coding assistant configuration
.codeium/instructions.md | 1 +
.continue/context.md | 1 +
.cursorrules | 1 +
.github/copilot-instructions.md | 1 +
.gitignore | 10 ++
.windsurfrules | 1 +
CLAUDE.md | 1 +
GEMINI.md | 1 +
README | 184 ++++++++++++++++++++++++++++++--
9 files changed, 190 insertions(+), 11 deletions(-)
create mode 100644 .codeium/instructions.md
create mode 100644 .continue/context.md
create mode 100644 .cursorrules
create mode 100644 .github/copilot-instructions.md
create mode 100644 .windsurfrules
create mode 100644 CLAUDE.md
create mode 100644 GEMINI.md
--
2.39.5
next reply other threads:[~2025-08-09 23:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 23:40 Sasha Levin [this message]
2025-08-09 23:40 ` [PATCH v2 1/2] README: restructure with role-based documentation and guidelines Sasha Levin
2025-08-10 15:44 ` Joe Perches
2025-08-10 16:46 ` Sasha Levin
2025-08-11 0:10 ` Joe Perches
2025-08-11 0:06 ` Randy Dunlap
2025-08-11 8:22 ` Geert Uytterhoeven
2025-08-11 15:48 ` Sasha Levin
2025-08-15 6:19 ` Kees Cook
2025-08-09 23:40 ` [PATCH v2 2/2] agents: add unified agent coding assistant configuration Sasha Levin
2025-08-10 7:01 ` Greg KH
2025-08-10 14:22 ` Sasha Levin
2025-08-14 0:36 ` Steven Rostedt
2025-08-15 6:23 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250809234008.1540324-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=corbet@lwn.net \
--cc=josh@joshtriplett.org \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox