mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: workflows@vger.kernel.org, ksummit@lists.linux.dev,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
	broonie@kernel.org, tytso@mit.edu
Subject: Re: [PATCH 1/2] agents: add infrastructure for agent resources
Date: Fri, 9 Oct 2026 12:27:33 +0200	[thread overview]
Message-ID: <2026100955-enchanted-magnetize-0d26@gregkh> (raw)
In-Reply-To: <5dfafd6f79165526fe17774c55b553b7dfe4b3fe.1791499378.git.sashal@kernel.org>

On Thu, Oct 08, 2026 at 06:54:52PM -0400, Sasha Levin wrote:
> Add agents/ as a home for skills, prompts, and other resources for coding
> assistants. Describe the skill layout and how to read the procedures in
> coding-assistants.rst, and add a MAINTAINERS entry covering agents/.
> 
> Assisted-by: LLM
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
>  Documentation/process/coding-assistants.rst | 12 ++++++++++++
>  MAINTAINERS                                 |  6 ++++++
>  2 files changed, 18 insertions(+)
> 
> diff --git a/Documentation/process/coding-assistants.rst b/Documentation/process/coding-assistants.rst
> index 051f0d819f68e..3288b32e993f5 100644
> --- a/Documentation/process/coding-assistants.rst
> +++ b/Documentation/process/coding-assistants.rst
> @@ -19,6 +19,18 @@ For guidelines on content generated by AI coding assistants see:
>  
>  * Documentation/process/generated-content.rst
>  
> +Agent resources
> +===============
> +
> +The ``agents/`` directory holds skills, prompts, and other resources for
> +coding assistants.
> +
> +Skills live under ``agents/skills/<name>/``, with a ``SKILL.md`` entry point
> +in the `Agent Skills format
> +<https://agentskills.io/specification>`_. Read the relevant resource
> +directly from its repository path. Links within a skill are relative to
> +that skill's directory.

Will this "solve" the issue where AGENTS.md is not present and so some
do not actually read this file?  Or is that a separate issue that will
be resolved with the symlink patch?

thanks,

greg k-h

  reply	other threads:[~2026-10-09 10:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 22:54 [PATCH 0/2] agents: add portable agent skills and Fixes attribution Sasha Levin
2026-10-08 22:54 ` [PATCH 1/2] agents: add infrastructure for agent resources Sasha Levin
2026-10-09 10:27   ` Greg KH [this message]
2026-10-09 10:35     ` Sasha Levin
2026-10-09 10:53       ` Greg KH
2026-10-09 13:40   ` Leon Romanovsky
2026-10-09 14:20     ` Sasha Levin
2026-10-09 14:22       ` Konstantin Ryabitsev
2026-10-09 16:36         ` Leon Romanovsky
2026-10-08 22:54 ` [PATCH 2/2] agents: add a skill to determine Fixes tags Sasha Levin
2026-10-09  9:42 ` [PATCH 0/2] agents: add portable agent skills and Fixes attribution Laurent Pinchart
2026-10-09 10:11   ` Sasha Levin
2026-10-09 16:30     ` Theodore Tso

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=2026100955-enchanted-magnetize-0d26@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tytso@mit.edu \
    --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

all inboxes | Powered by JetHome®