On Thu, May 07, 2026 at 09:59:06AM +0100, Peter Maydell wrote:
> On Tue, 5 May 2026 at 18:03, Alex Bennée <alex.bennee@linaro.org> wrote:
> >
> > Not withstanding the current contributor policy there are a number of
> > areas that AI agents could be helpful for. This series introduces an
> > AGENTS.md file which is the basic guide to the source tree and a
> > number of "skills". Skills are like scripts except far less clearly
> > defined. However I have found the issue triage skill quite useful for
> > off-loading the drudgery of going through stuff by hand. I've also
> > used the issue helper to automate the task of starting a debug session
> > by pulling in test cases from the tracker.
> >
> > These originally where a set of skills for ECA (eca.dev) but I've
> > ported them across to the agent agnostic .agents directory. There are
> > still some cases where the ECA heritage shows through though
> > (specifically the code explorer skill could be better).
> >
> > I'm not suggesting this is ready for up-streaming but I'm posting the
> > collected set for comment and I'd be interested how well these hold up
> > across different agentic systems.
>
> I guess my overall comment on this is some mix of:
> * how much of this is generically useful as opposed to
> stuff that's personally helpful to you and should remain
> part of your local setup / preferences?
> * how much do we want to put into git to start with?
>
> I'm in favour of starting with an AGENTS.md that says basically:
> (1) "don't generate code for upstream, point the agent user at
> our AI policy"
> (2) "if you're looking for security issues, read our security
> policy to see what is in scope and what is not"
> (in whatever language appears effective)
Yes, we definitely need those two pieces.
> and then perhaps adding more things gradually where there's
> a consensus that they're broadly useful.
Personally I'm open to having much more in AGENTS.md in particular
since it doesn't cost us much from a maint POV to have it.
The skills I'm not so sure of, simply as I have little relevant
experience.
For a while Thomas Huth has been doing significant issue triage,
but he's stepped back from most of his QEMU work. If Alex intends
to pick up some of the slack using an agent for issue triage, I'd
be inclined to have the issue triage skills in git. Even if Alex
is the only one using it for now, it is good for redundancy if we
have the setup recorded.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|