Re: [RFC PATCH 08/10] .agents/skills: add qemu-issue-triage agent skill

["Daniel P. Berrangé" <berrange@redhat.com>]

On Thu, May 07, 2026 at 01:32:59PM +0100, Alex Bennée wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
> 
> > On Tue, May 05, 2026 at 06:01:03PM +0100, Alex Bennée wrote:
> >> While triaging the issue tracker I wondered if this would be a
> >> suitable job for an AI agent. Unfortunately the OSS program doesn't
> >> give any credits to run agents in gitlab. However I do have access to
> >> models from my editor and ECA so I built one and tested it on a few
> >> issues.
> >> 
> >> Obviously this can't apply as is because it probably encodes too much
> >> of my local setup (using pass for API keys) and uses the ECA as my
> >> preferred coding agent. I assume at some point there will be agreement
> >> between all the agents where skill live.
> >> 
> >> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> >
> > ..snip..
> >
> >> diff --git a/.agents/skills/qemu-issue-triage/assets/labels.txt
> >> b/.agents/skills/qemu-issue-triage/assets/labels.txt
> >> new file mode 100644
> >> index 00000000000..d329f34183d
> >> --- /dev/null
> >> +++ b/.agents/skills/qemu-issue-triage/assets/labels.txt
> >
> > Seeing our labels listed like this triggers my urge to "tidy" :-)
> >
> > Don't take anything below to be a complaint / blocker about this patch.
> > This patch is fine in so much as it faithfully represents the mess we
> > have created in gitlab.
> >
> >> @@ -0,0 +1,133 @@
> >> +# SPDX-License-Identifier: GPL-2.0-or-later
> >> +ACPI                       Power Management related (ACPI / SMBIOS / HEST / GHES)
> >> +Audio Audio devices; both backend (host audio) and frontend (guest
> >> audio)
> >
> > Mixing frontend and backend is a bad idea in general IMHO.
> >
> > I feel like we should also have an explicit label for each backend, for
> > both audio and every other backend type.
> 
> Backend: chardev
> Backend: audio
> ?

No sorry, I meant  chardev:socket, chardev:stdio, chardev:mux, etc and
audio:dsound, audio:alsa, audio:pa, etc


> >> +GUI Graphical User Interface (gtk, SDL, curses, VNC, spice, ...)
> >> +GUI::Cocoa                 Cocoa
> >> +GUI::DBus                  DBus
> >> +GUI::GTK
> >> +GUI::SDL                   SDL
> >> +GUI::SPICE                 SPICE
> >
> > spice is duplicated later
> 
> Prompt: "find all the issues with the "spice" label and label them with the GUI::SPICE label instead"
> 
> the result was:
> 
>   general: relabling spice issues (5 steps, 13.5K / 1M) ✅ 1m 26s
> 
>   I have successfully relabeled all GitLab issues in the `qemu-project/qemu` repository by replacing the "spice" label with the "GUI::SPICE" label.
> 
>   ### Summary of Actions:
>   - **Total Issues Updated**: 21 (including both open and closed issues).
>   - **Relabeling**: Removed the `spice` label and applied the `GUI::SPICE` label to each identified issue.
>   - **Verification**: Confirmed that `glab issue list --label spice` now returns no results, while `glab issue list --label "GUI::SPICE"` includes all updated issues.
> 
>   ### Updated Issues:
>   The following 21 issues were updated: 
>   `3148`, `3070`, `2860`, `2667`, `2639`, `2561`, `2411`, `2335`, `2282`, `2071`, `1926`, `1829`, `1778`, `1777`, `1553`, `1549`, `1431`, `1426`, `1285`, `681`, `232`.
> 
> about 0.08p in inference costs.
> 

> > What's this for, and why : instead of :: ?
> 
> No idea - is this the mechanism we use to hide live security issues?

security issues should not be in the issue tracker at all

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 :|