Update Avm Modules In Bicep
GitHubOfficialOriginally contributed by @PlagueHO as prompts/update-avm-modules-in-bicep.prompt.md; moved into a skill by pull request #761Distributed by GitHub
- Skill
- Workflow
- Cloud and DevOps
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured workflow for maintaining Azure Verified Modules (AVM) in Bicep infrastructure-as-code files. It scans existing files, identifies current module versions, compares them against the latest releases from the Microsoft Container Registry, and performs the necessary updates. The process includes validation steps to ensure the resulting Bicep files remain compliant and functional, while implementing a safety pause for any updates involving breaking changes or security modifications.
What it does
- Scans Bicep files to extract current AVM module versions.
- Queries the Microsoft Container Registry to identify the latest available module versions.
- Compares versions and applies updates to Bicep files automatically.
- Validates updated files using Bicep linting and build commands.
- Provides a structured summary table detailing update status and documentation links.
- Triggers a manual review pause for breaking changes or security-sensitive updates.
When to use it
- When you need to ensure your infrastructure-as-code uses the most recent, supported AVM versions.
- When managing multiple Bicep files that rely on Azure Verified Modules.
- When you want to automate the tedious process of checking and updating module tags.
- When you need to maintain compliance with the latest module standards.
Advantages
- Reduces manual effort in tracking and updating module versions.
- Ensures infrastructure consistency by standardizing on the latest module releases.
- Maintains file integrity through automated linting and build validation.
- Provides clear visibility into update status and potential breaking changes.
Usage examples
- “Update all AVM modules in main.bicep to the latest versions.”
- The agent scans main.bicep, identifies outdated modules, updates them to the latest versions, validates the file, and presents a summary table of changes.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/github/update-avm-modules-in-bicep/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip update-avm-modules-in-bicep.zip -d .agents/skills
Documentation by PlagueHO
Update Azure Verified Modules in Bicep Files
Update Bicep file ${file} to use latest Azure Verified Module (AVM) versions. Limit progress updates to non-breaking changes. Don't output information other than the final output table and summary.
Process
Scan: Extract AVM modules and current versions from
${file}Identify: List all unique AVM modules used by matching
avm/res/{service}/{resource}using#searchtoolCheck: Use
#fetchtool to get latest version of each AVM module from MCR:https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/listCompare: Parse semantic versions to identify AVM modules needing update
Review: For breaking changes, use
#fetchtool to get docs from:https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}Update: Apply version updates and parameter changes using
#editFilestoolValidate: Run
bicep lintandbicep buildusing#runCommandstool to ensure compliance.Output: Summarize changes in a table format with summary of updates below.
Tool Usage
Always use tools #search, #searchResults,#fetch, #editFiles, #runCommands, #todos if available. Avoid writing code to perform tasks.
Breaking Change Policy
⚠️ PAUSE for approval if updates involve:
Incompatible parameter changes
Security/compliance modifications
Behavioral changes
Output Format
Only display results in table with icons:
| Module | Current | Latest | Status | Action | Docs |
|--------|---------|--------|--------|--------|------|
| avm/res/compute/vm | 0.1.0 | 0.2.0 | 🔄 | Updated | [📖](link) |
| avm/res/storage/account | 0.3.0 | 0.3.0 | ✅ | Current | [📖](link) |
### Summary of Updates
Describe updates made, any manual reviews needed or issues encountered.Icons
🔄 Updated
✅ Current
⚠️ Manual review required
❌ Failed
📖 Documentation
Requirements
Use MCR tags API only for version discovery
Parse JSON tags array and sort by semantic versioning
Maintain Bicep file validity and linting compliance
Files
- ATTRIBUTION.mdAdded by AutoGineer1.2 KiB
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.2 KiB
Requirements and compatibility
Written for: GitHub Copilot
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Names Copilot tools, Needs network access
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Originally contributed by
@PlagueHOas prompts/update-avm-modules-in-bicep.prompt.mdmoved into a skill by pull request #761
- Publisher
- GitHub (Official)
- Distributed by
- GitHub
- Source
- github/awesome-copilot · skills/update-avm-modules-in-bicep · commit 797337f
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Contributors
- PlagueHO, CypherHK, derekclair, jeremykohn
AutoGineer is not affiliated with or endorsed by PlagueHO or GitHub.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download update-avm-modules-in-bicep.zip