[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AWN6DSKPX40MNWFHYX0MT":3,"skill-same:01M69AWN6DSKPX40MNWFHYX0MT":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M69AWN6DSKPX40MNWFHYX0MT","azldev-update-component",null,"Read this before finalizing a component change, changing source resolution, or touching a lock file; lock edits are easy to get wrong. Explains how to refresh azldev component lock files with 'azldev comp update', covering when to run update versus render, the update\u002Frender\u002Fcommit\u002Fre-render\u002Famend workflow, and per-component versus -a refresh. Triggers include comp update, refresh lock, bump pin, change snapshot, upstream distro, lock drift, version bump, finalize component.","microsoft\u002Fazurelinux","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AVY9Y3D59ZBRVNKRJ851E",5364,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fazldev-update-component\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"component","azldev update component","azldev","update","bump","when","re","render","comp","how to","triggers","get","upstream","drift","files","workflow","version","pin","file","commit","change","2026-11-10 10:12:30",false,"---\nname: azldev-update-component\ndescription: \"Read this before finalizing a component change, changing source resolution, or touching a lock file; lock edits are easy to get wrong. Explains how to refresh azldev component lock files with 'azldev comp update', covering when to run update versus render, the update\u002Frender\u002Fcommit\u002Fre-render\u002Famend workflow, and per-component versus -a refresh. Triggers include comp update, refresh lock, bump pin, change snapshot, upstream distro, lock drift, version bump, finalize component.\"\n---\n\n# Update component lock files\n\n`azldev comp update` (`comp` is an alias for `component`) refreshes one or more\ncomponent lock files under `locks\u002F`. A lock pins the resolved upstream commit plus\nan input fingerprint computed from the component's render inputs — its TOML config,\noverlays, the pinned upstream commit, and the distro release version. If any of\nthose change, the lock is stale.\n\n## When to run `update`\n\n| Situation | Run `update`? |\n| --- | --- |\n| Adding a new upstream component (no lock yet) | **Yes** — first, to create the lock before `render`\u002F`build` can resolve it |\n| Finalizing a component change for a PR | **Yes** — once at the end |\n| Changing source resolution (commit pin, upstream distro\u002Fversion, or snapshot) | **Yes** — also mid-workflow (see below) |\n| Iterating on overlays \u002F build config \u002F metadata | No — once the lock exists, `render` alone is enough while iterating |\n| Just reading or building existing components | No |\n\nRefresh a single component with `-p \u003Cname>`. Use `-a` (all components) only for\ncoordinated mass refreshes (e.g. a new distro snapshot) or when investigating\nlock drift across many components — it is slow. For day-to-day work use `-p`. Add\n`-O json` for machine-readable lock output when debugging.\n\n## End-of-work refresh (the common case)\n\nFor most edits — overlays, build flags, metadata — run `update` once at the end,\nthen re-render *after committing* so the generated changelog and release reflect\nyour new commit:\n\n```sh\nazldev comp update -p \u003Cname>\nazldev comp render -p \u003Cname>\ngit add \u003Cchanged-component-config-and-source-paths> \\\n\tlocks\u002F\u003Cname>.lock \\\n\tspecs\u002F\u003Cfirst-char>\u002F\u003Cname>\u002F\ngit commit -m \"fix(\u003Cname>): ...\"\n\n# Re-render and amend so the changelog \u002F Release: track the new commit.\nazldev comp render -p \u003Cname>\ngit add specs\u002F\u003Cfirst-char>\u002F\u003Cname>\u002F\ngit commit --amend --no-edit\n```\n\n### Why the second render-and-amend?\n\nChangelog generation and release calculation are separate. When a spec uses\n`%autochangelog`, rpmautospec derives it from the component's **git history** for\nevery release mode. For non-manual release modes, azldev also derives or bumps\n`Release:` from that history. The first render happens before your commit exists,\nso a fresh render *after* committing incorporates the new changelog entry and any\nautomatic release bump. Amending folds that output into a single clean commit and\nkeeps rendered-spec \u002F lock CI gates (which run against committed state) green.\n\nFor a component with `release.calculation = \"manual\"`, increment the release\ncounter yourself in the same change. Manual mode is not an exemption from the\npost-commit render-stage-amend cycle: when the spec uses `%autochangelog`, that\nrender incorporates the new commit.\n\n## Changing source resolution\n\nA source-resolution change follows the same rule, using one commit followed by a\npost-render amend:\n\n1. Change the commit pin, upstream distro\u002Fversion, or snapshot, then `azldev comp update -p \u003Cname>`; sanity-check `locks\u002F\u003Cname>.lock`.\n2. `azldev comp render -p \u003Cname>` — the spec body now tracks the newly resolved source. `%changelog` \u002F `Release:` still reflect the previous source; that is expected until you commit.\n3. Iterate on overlays \u002F patches \u002F build config as the new source requires, re-rendering after each change. Re-run `update` only if you change a source-resolution input again.\n4. `azldev comp update -p \u003Cname>`, then stage and commit all component inputs changed above with the refreshed lock and rendered output:\n\n   ```sh\n   git add \u003Cchanged-component-config-and-source-paths> \\\n\t   locks\u002F\u003Cname>.lock \\\n\t   specs\u002F\u003Cfirst-char>\u002F\u003Cname>\u002F\n   git commit -m \"update(\u003Cname>): ...\"\n   ```\n5. `azldev comp render -p \u003Cname>` — `%changelog` \u002F `Release:` now reflect the new lock.\n6. `git add specs\u002F\u003Cfirst-char>\u002F\u003Cname>\u002F`, then `git commit --amend --no-edit` so the source change and rendered output land together.\n\nGenerated by `azldev docs agent`; do not hand-edit.\n","# Update component lock files\n\n`azldev comp update` (`comp` is an alias for `component`) refreshes one or more\ncomponent lock files under `locks\u002F`. A lock pins the resolved upstream commit plus\nan input fingerprint computed from the component's render inputs — its TOML config,\noverlays, the pinned upstream commit, and the distro release version. If any of\nthose change, the lock is stale.\n\n## When to run `update`\n\n| Situation | Run `update`? |\n| --- | --- |\n| Adding a new upstream component (no lock yet) | **Yes** — first, to create the lock before `render`\u002F`build` can resolve it |\n| Finalizing a component change for a PR | **Yes** — once at the end |\n| Changing source resolution (commit pin, upstream distro\u002Fversion, or snapshot) | **Yes** — also mid-workflow (see below) |\n| Iterating on overlays \u002F build config \u002F metadata | No — once the lock exists, `render` alone is enough while iterating |\n| Just reading or building existing components | No |\n\nRefresh a single component with `-p \u003Cname>`. Use `-a` (all components) only for\ncoordinated mass refreshes (e.g. a new distro snapshot) or when investigating\nlock drift across many components — it is slow. For day-to-day work use `-p`. Add\n`-O json` for machine-readable lock output when debugging.\n\n## End-of-work refresh (the common case)\n\nFor most edits — overlays, build flags, metadata — run `update` once at the end,\nthen re-render *after committing* so the generated changelog and release reflect\nyour new commit:\n\n```sh\nazldev comp update -p \u003Cname>\nazldev comp render -p \u003Cname>\ngit add \u003Cchanged-component-config-and-source-paths> \\\n\tlocks\u002F\u003Cname>.lock \\\n\tspecs\u002F\u003Cfirst-char>\u002F\u003Cname>\u002F\ngit commit -m \"fix(\u003Cname>): ...\"\n\n# Re-render and amend so the changelog \u002F Release: track the new commit.\nazldev comp render -p \u003Cname>\ngit add specs\u002F\u003Cfirst-char>\u002F\u003Cname>\u002F\ngit commit --amend --no-edit\n```\n\n### Why the second render-and-amend?\n\nChangelog generation and release calculation are separate. When a spec uses\n`%autochangelog`, rpmautospec derives it from the component's **git history** for\nevery release mode. For non-manual release modes, azldev also derives or bumps\n`Release:` from that history. The first render happens before your commit exists,\nso a fresh render *after* committing incorporates the new changelog entry and any\nautomatic release bump. Amending folds that output into a single clean commit and\nkeeps rendered-spec \u002F lock CI gates (which run against committed state) green.\n\nFor a component with `release.calculation = \"manual\"`, increment the release\ncounter yourself in the same change. Manual mode is not an exemption from the\npost-commit render-stage-amend cycle: when the spec uses `%autochangelog`, that\nrender incorporates the new commit.\n\n## Changing source resolution\n\nA source-resolution change follows the same rule, using one commit followed by a\npost-render amend:\n\n1. Change the commit pin, upstream distro\u002Fversion, or snapshot, then `azldev comp update -p \u003Cname>`; sanity-check `locks\u002F\u003Cname>.lock`.\n2. `azldev comp render -p \u003Cname>` — the spec body now tracks the newly resolved source. `%changelog` \u002F `Release:` still reflect the previous source; that is expected until you commit.\n3. Iterate on overlays \u002F patches \u002F build config as the new source requires, re-rendering after each change. Re-run `update` only if you change a source-resolution input again.\n4. `azldev comp update -p \u003Cname>`, then stage and commit all component inputs changed above with the refreshed lock and rendered output:\n\n   ```sh\n   git add \u003Cchanged-component-config-and-source-paths> \\\n\t   locks\u002F\u003Cname>.lock \\\n\t   specs\u002F\u003Cfirst-char>\u002F\u003Cname>\u002F\n   git commit -m \"update(\u003Cname>): ...\"\n   ```\n5. `azldev comp render -p \u003Cname>` — `%changelog` \u002F `Release:` now reflect the new lock.\n6. `git add specs\u002F\u003Cfirst-char>\u002F\u003Cname>\u002F`, then `git commit --amend --no-edit` so the source change and rendered output land together.\n\nGenerated by `azldev docs agent`; do not hand-edit.\n",{"name":5,"description":7},"4.0","431ad36a7a827e8ec414e96ae75517ec1ded115d",".agents\u002Fskills\u002Fazldev-update-component",714,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 02:36:52",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add microsoft\u002Fazurelinux --skill azldev-update-component",{"tool":60,"command":61},"bunx","bunx skills add microsoft\u002Fazurelinux --skill azldev-update-component",{"tool":63,"command":64},"pnpm","pnpm dlx skills add microsoft\u002Fazurelinux --skill azldev-update-component","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fazldev-update-component\u002FSKILL.md",true,[],[69,98,120,144,165,189],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":40},"01M69AX4PP9MJPS4TE3XDW93NJ","skill-metrics","[Skill] metrics, azure-monitor, aks - Query Azure Monitor metrics for Koji AKS node CPU, memory, disk usage, and pod readiness.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-metrics\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"skill metrics","metrics","memory","azure","monitor","azure-monitor","aks","disk","node","query","azure monitor","false","readiness","CPU","disk usage","usage","for",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":40},"01M69AX2WT9YWZTVMMQ6QWHG3Y","skill-mass-triage","[Skill] Batch-triage build failures from a JSON results file — diagnose with parallel sub-agents, bucketize by root cause, and produce a consolidated summary. Use when asked to triage a Koji results file. Triggers: batch triage, mass triage, triage results file, bucketize failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-mass-triage\u002FSKILL.md",[104],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[106,107,108,109,110,37,111,112,113,114,115,116,29,117,118,119,24],"triage","skill mass triage","diagnose","produce","batch","json","parallel","results","use","build","summary","with","root","root cause",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":130,"publishedAt":40},"01M69AX11X7RJS8A0GBJV2X0WD","skill-kql-queries","[Skill] kql, queries, log analytics, container logs - KQL query templates for Koji container logs, pod errors, restarts, Kubernetes events, build job activity, and node resource usage via Log Analytics.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-kql-queries\u002FSKILL.md",[126,129],{"categoryNo":127,"categoryName":128,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[131,132,133,134,135,136,137,89,138,139,115,90,92,140,141,142,143,96,97],"skill kql queries","kql","queries","kubernetes","analytics","logs","templates","container","log","events","via","activity","errors",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":40},"01M69AWYRJY05J3N3K9PZ0X38H","skill-koji-triage","[Skill] Examine Koji builds, fetch task info and logs from the Koji Web UI, identify failures, and provide root cause analysis. Use when triaging Koji build failures, investigating failed tasks, downloading build logs, or searching for broken packages. Triggers: koji failure, koji build failed, koji task, koji log, koji triage, build failure analysis.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-koji-triage\u002FSKILL.md",[150],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[106,152,153,154,155,156,157,136,158,159,160,114,139,161,162,29,163,164,97,119,24],"skill koji triage","web","root cause analysis","tasks","packages","ui","analysis","broken","fetch","task","info","failure analysis","web ui",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":40},"01M69AWWNGM4S4DDN6MSXMJ1XY","skill-fedora-mirror-injections","[Skill] Diagnose Azure Linux Stage 1 (bootstrap-mirror) BuildRequires resolution failures and backfill missing RPMs into the prod Fedora updates mirror via the azl-infra injections file. Use when triaging stage-1 \u002F azl4-bootstrap-mirror build failures, finding dependency gaps in the Fedora mirror, deciding whether a failure is a real mirror gap vs a transient timeout or a spec bug, adding entries to azl4-stage1-injections.yaml, or opening a PR with mirror injections. Triggers: bootstrap-mirror, stage 1 build failure, fedora mirror gap, missing BuildRequires, nothing provides crate, no match for argument, injections file, azl4-stage1-injections, mirror injection.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-fedora-mirror-injections\u002FSKILL.md",[171],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[173,174,175,176,177,108,84,178,179,180,114,181,182,183,184,29,185,186,187,97,188,24],"skill fedora mirror injections","fedora","mirror","spec","linux","pr","bootstrap","injection","dependency","bug","infra","entries","missing","argument","updates","backfill",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":40},"01M69AWTVNFMTX4KQVR6EK62C0","skill-deployment-context","[Skill] deployment context, aks, azure, koji - Resolve Koji AKS deployment context -- resource group, cluster name, subscription, Log Analytics workspace, and monitoring resource names from deployment_summary.yaml when available, or discover them dynamically from Azure.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-deployment-context\u002FSKILL.md",[195],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[197,198,199,135,84,200,201,87,202,139,116,203,92,204,205,24],"skill deployment context","deployment","context","yaml","monitoring","workspace","discover","name","cluster"]