On Thu, May 07, 2026 at 11:24:37AM +0200, Philippe Mathieu-Daudé wrote: > On 7/5/26 10:59, Peter Maydell wrote: > > On Tue, 5 May 2026 at 18:03, Alex Bennée <[email protected]> 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? > > Parts could be shared under a 'qemu' folder within mainstream > review-prompts project: > > https://github.com/masoncl/review-prompts
IMHO it is more likely to stay updated and relevant if it is maintained directly in qemu.git where it is visible to our manitainers. 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 :|
