From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E7C942E54D1; Fri, 9 Oct 2026 10:27:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791541658; cv=none; b=qU4Q5twzB74Mh7DY8ceQVd9vcbadiRLN8DYYwxZO8zGvKiVJHtOn5R3QHRBKu6yll7cMcxqMfhyfksBsfSSOH7YeE++fRzbaJgRTLQysIYBdPLg5R4mMkJDl8kVO5fkhixMTVbp5P0DDcwFx+AMQml5cA/aIo5opMJgbqDejDu8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791541658; c=relaxed/simple; bh=7PAZE05Vz4DM+YFPn0VEQR4RHMWcPjbnYv99K7hgB+4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=k+lUDJno1w5p9YdH3NkKI0Y7qlLc3ZJFxdhvBBNvNspxjhY8aPCMNvadxvrTxgNkgt22N3D/InA1Omcbp3n15HMNTT6TDzWipSguSjdWST4LPUIMMnQEFgN82BxZcAOhILxBv0/WCb+fCmrTgsonlJGBUOlU6I6X2c99j5NY7Sg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ZYYPKKw3; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="ZYYPKKw3" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A6A8E1F000FF; Fri, 9 Oct 2026 10:27:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1791541656; bh=lZDb/vIh8j/9PYXSKfXKTg1H5WkNkFAEgYTNZ3b8PEQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ZYYPKKw3fGmaSciV8UlwtF5ifosPnON3WHeYNbiLRg7pbtwew1mcBW/+fRHpV8WDs xffjjhEjO4hWfpiKxulHxAe4pfSvA6WXYo/W5hwNjv2i8aqiVb2SbWZlYCVu70Hfvl TQtflJOtgHtSn+cMPsqt/M8JWjZFW3F+Vg764rmY= Date: Fri, 9 Oct 2026 12:27:33 +0200 From: Greg KH To: Sasha Levin 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 Message-ID: <2026100955-enchanted-magnetize-0d26@gregkh> References: <5dfafd6f79165526fe17774c55b553b7dfe4b3fe.1791499378.git.sashal@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 > --- > 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//``, with a ``SKILL.md`` entry point > +in the `Agent Skills format > +`_. 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