Daniel P. Berrangé <[email protected]> writes:

> On Mon, May 11, 2026 at 06:04:52PM +0100, Alex Bennée wrote:
>> This provides a skill detailing how to explore the QEMU code base. It
>> guides the agents to use the tags and git-grep by default and outlines
>> some of the confusions that can occur with multiple build directories.
>> 
>> Signed-off-by: Alex Bennée <[email protected]>
>> 
>> ---
>> v2
>>   - remove personal gtag skill references, add global stanzas directly
>>   - moved macro information from AGENTS.md into code explorer
>>   - more imperative language to trigger its use
>>   - add section on using scripts/expand_macro.py
>>   - remove eca reference from evals.json (maybe we should just drop this)
>> ---
>>  .agents/skills/qemu-code-explorer/SKILL.md    | 119 ++++++++++++++++++
>>  .../qemu-code-explorer/evals/evals.json       |  26 ++++
>>  AGENTS.md                                     |   1 +
>>  3 files changed, 146 insertions(+)
>>  create mode 100644 .agents/skills/qemu-code-explorer/SKILL.md
>>  create mode 100644 .agents/skills/qemu-code-explorer/evals/evals.json
>> 
>> diff --git a/.agents/skills/qemu-code-explorer/SKILL.md 
>> b/.agents/skills/qemu-code-explorer/SKILL.md
>> new file mode 100644
>> index 00000000000..d5b7d6a35cd
>> --- /dev/null
>> +++ b/.agents/skills/qemu-code-explorer/SKILL.md
>> @@ -0,0 +1,119 @@
>> +---
>> +name: qemu-code-explorer
>> +description: Systematic framework for deep-diving into the QEMU codebase. 
>> Use this to find precise symbol definitions (functions, structs, globals), 
>> locate all call sites or references, explore subsystem architectures, or 
>> search generated code in build directories. You MUST use this skill when 
>> exploring code flow and dependencies.
>> +license: GPL-2.0-or-later
>
> Is "license:" a mandatory tag from a schema we're following here,
> or can be used "SPDX-License-Identifier:" instead ?

It's from the spec: https://agentskills.io/specification#frontmatter

>
>
> With regards,
> Daniel

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro

Reply via email to