Update Avm Modules In Bicep

Here's a skill that automates the tedious process of keeping Azure Verified Modules current in your Bicep infrastructure files. It scans your Bicep templates, checks the Microsoft Container Registry for latest AVM versions, and updates module references while running bicep lint and build validation to catch issues. The smart part is it only applies non-breaking updates automatically and pauses for approval when it detects parameter changes or security modifications that need human review. Saves you from manually tracking down version numbers and ensures your infrastructure code stays compliant with current AVM standards without breaking existing deployments.