skill-update-component
[Skill] Refresh component lock files with azldev comp update. Use when finalizing a component change for PR, bumping an upstream commit pin, or investigating lock-drift CI failures. Triggers: comp update, refresh lock, bump pin, lock drift, version bump, finalize component change. Published by microsoft in azurelinux.
What is skill-update-component?
[Skill] Refresh component lock files with azldev comp update. Use when finalizing a component change for PR, bumping an upstream commit pin, or investigating lock-drift CI failures. Triggers: comp update, refresh lock, bump pin, lock drift, version bump, finalize component change. Published by microsoft in azurelinux. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using azurelinux
Technical details
- Install or run with Copy skill directory
When to use skill-update-component
- Use it for developers using azurelinux.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/azurelinux
- Skill file: .github/skills/skill-update-component/SKILL.md
What it does
[Skill] Refresh component lock files with azldev comp update. Use when finalizing a component change for PR, bumping an upstream commit pin, or investigating lock-drift CI failures. Triggers: comp update, refresh lock, bump pin, lock drift, version bump, finalize component change.
Skill instructions
Update Component Lock Files azldev comp update refreshes one or more component lock files in locks/. A lock file pins the upstream commit + an input fingerprint computed from the component's TOML config; if either changes, the lock is stale and the Update Locks CI check fails. When to run it | Situation | Run update? | |-----------|---------------| | Finalizing any component change for PR | Yes — once at the end | | Bumping an upstream commit pin | Yes — also mid-workflow (see below) | | Iterative overlay/build-config/metadata edits | No — render alone is enough during iteration See section on changelog/release quirks in the pin-bump workflow below | | Just reading or building existing components | No | Always re-run update before opening a PR, even if all you did was tweak an overlay description. The fingerprint is computed from the full component config, so any TOML change may invalidate the lock. End-of-work refresh (the common case) For most component edits — overlays, build flags,
Explore related resources
Frequently asked questions
What is skill-update-component?
skill-update-component is a open-source AI agent skill with Copy skill directory. [Skill] Refresh component lock files with azldev comp update. Use when finalizing a component change for PR, bumping an upstream commit pin, or investigating lock-drift CI failures.
Who is skill-update-component best for?
skill-update-component is best for reusing agent instructions, scripts, and references.
How do I install skill-update-component?
Install or run skill-update-component using Copy skill directory. Check skill-update-component for the latest setup command.
Is skill-update-component actively maintained?
skill-update-component may need a closer maintenance check before production use.
Auto-fetched from GitHub.
