Azldev Update Component

What it does

When your agent uses it

• Include comp update
• Change snapshot
• Upstream distro
• Finalize component

Example prompts

• “azldev comp update”
• “/azldev-update-component”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Change the commit pin, upstream distro/version, or snapshot, then azldev comp update -p ; sanity-check locks/.lock.
2. 2azldev comp render -p — the spec body now tracks the newly resolved source. %changelog / Release: still reflect the previous source; that…
3. 3Iterate on overlays / patches / build config as the new source requires, re-rendering after each change. Re-run update only if you change…
4. 4azldev comp update -p , then stage and commit all component inputs changed above with the refreshed lock and rendered output
5. 5azldev comp render -p — %changelog / Release: now reflect the new lock.
6. 6git add specs///, then git commit --amend --no-edit so the source change and rendered output land together.

What it can do on your machine

Read from SKILL.md and the folder at commit f019108. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Azldev Update Component loads about 1.1k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 488 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~126

When it runs · the whole SKILL.md, loaded when a task matches

~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/azurelinux at commit f019108, republished under its MIT licence (© microsoft). 488 words, ~1,117 tokens.

name

azldev-update-component

description

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/render/commit/re-render/amend 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.

azldev comp update -p <name>
azldev comp render -p <name>
git add <changed-component-config-and-source-paths> \
	locks/<name>.lock \
	specs/<first-char>/<name>/
git commit -m "fix(<name>): ..."

# Re-render and amend so the changelog / Release: track the new commit.
azldev comp render -p <name>
git add specs/<first-char>/<name>/
git commit --amend --no-edit

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/azldev-update-component of microsoft/azurelinux.

Open the folder on GitHubat commit f019108