azure-infra-review
A checklist-based tool for reviewing Azure infrastructure changes, ensuring naming and security standards are met.
Install
mkdir -p .claude/skills/azure-infra-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16631" && unzip -o skill.zip -d .claude/skills/azure-infra-review && rm skill.zipInstalls to .claude/skills/azure-infra-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Reviews Bicep modules, azure.yaml, and infrastructure changes for the KB Agent project. Checks naming, RBAC, module wiring, and doc sync. Use when working on infra/ or reviewing infrastructure PRs.Key capabilities
- →Review Bicep modules for correctness
- →Verify `azure.yaml` configurations
- →Check resource naming conventions
- →Review RBAC and security settings
- →Validate module wiring and dependencies
How it works
The skill reviews infrastructure changes against a checklist covering naming conventions, RBAC, module wiring, service definitions, and documentation synchronization.
Inputs & outputs
When to use azure-infra-review
- →Review infrastructure pull request
- →Verify RBAC in Bicep modules
- →Update Azure resource naming
- →Sync infrastructure documentation
About this skill
Azure Infrastructure Review
Review infrastructure changes for correctness, convention compliance, and documentation sync.
Module Structure
infra/
├── azure/
│ ├── azure.yaml # AZD project definition
│ ├── hooks/ # AZD pre/post-provision hooks
│ └── infra/
│ ├── main.bicep # Orchestration — wires all modules + role assignments
│ ├── main.parameters.json # AZD parameter file
│ └── modules/
│ ├── monitoring.bicep # Log Analytics + Application Insights
│ ├── storage.bicep # Storage account with containers + RBAC
│ ├── ai-services.bicep # AI Services + model deployments + RBAC
│ ├── search.bicep # AI Search service + RBAC
│ ├── foundry-project.bicep # Foundry project
│ ├── cosmos-db.bicep # Cosmos DB NoSQL (serverless)
│ ├── cosmos-db-role.bicep # Cosmos DB native RBAC role
│ ├── function-app.bicep # Functions on Container Apps (Docker)
│ ├── container-registry.bicep # Azure Container Registry
│ ├── container-app.bicep # Container Apps Environment + web app
│ ├── container-apps-env.bicep # Container Apps Environment
│ ├── agent-container-app.bicep # Agent Container App
│ ├── apim.bicep # API Management
│ └── apim-agent-api.bicep # APIM agent API definition
└── docker/
├── docker-compose.dev-infra.yml
└── docker-compose.dev-services.yml
Review Checklist
Naming & Conventions
- Resource names follow
{type}-{projectName}-{env}pattern - Module file names are descriptive and kebab-case
- Parameters have descriptions and appropriate defaults
- Region: East US 2 (unless specific service requires otherwise)
RBAC & Security
- All role assignments defined in
infra/azure/infra/main.bicep— not in individual modules - Cosmos DB uses native RBAC via
cosmos-db-role.bicep— no connection strings - Managed identity used for all service-to-service auth
- No secrets or keys in module outputs
- No secrets in app settings — use managed identity references
Module Wiring
- New modules called from
infra/azure/infra/main.bicep - Module outputs consumed by dependent modules
- Role assignments connect the right identities to the right resources
- Dependencies expressed via module references (not
dependsOnstrings)
Service Definitions
-
infra/azure/azure.yamllists all 6 services with correct paths and hosts:agent→ Container App (Docker, port 8088)func-convert-cu→ Container App (Docker)func-convert-mistral→ Container App (Docker)func-convert-markitdown→ Container App (Docker)func-index→ Container App (Docker)web-app→ Container App (Docker)
- Docker contexts and Dockerfiles referenced correctly
Documentation Sync
-
docs/specs/infrastructure.mdupdated to reflect any resource changes - New resources documented with their purpose, SKU, and connectivity
Validation
- Bicep compiles:
az bicep build --file infra/azure/infra/main.bicep - Parameters file is valid JSON with correct structure
- No hardcoded subscription IDs, resource group names, or tenant IDs
Reference
When not to use it
- →When the changes are not related to Bicep modules or `azure.yaml`
- →When the project is not the KB Agent project
- →When the task is not reviewing infrastructure PRs
Limitations
- →The skill reviews Bicep modules, azure.yaml, and infrastructure changes for the KB Agent project
- →The skill checks naming, RBAC, module wiring, and documentation synchronization
- →The skill focuses on infrastructure changes in the `infra/` directory
How it compares
This skill provides a structured checklist for reviewing Azure infrastructure changes, ensuring compliance and consistency, unlike a manual review that might miss specific conventions.
Compared to similar skills
azure-infra-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| azure-infra-review (this skill) | 0 | 4mo | No flags | Intermediate |
| up | 0 | 3mo | Review | Intermediate |
| odoo-image-supply-chain | 0 | 4mo | No flags | Advanced |
| opnsense | 0 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by aldelar
View all by aldelar →You might also like
up
Azure-Samples
Creates an azd environment, checks prerequisites (RBAC, model quota), provisions the AI agent app infrastructure via `azd up`, and health-checks the deployed app.
odoo-image-supply-chain
Insightpulseai
Close container image supply-chain gap with automated ACR builds, vulnerability scanning, and image signing
opnsense
MylesLandais
OPNsense firewall + router for the SecretCon lab, deployed as a Proxmox VM in front of vmbr1
ops
denniszielke
>
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
storage-networking
pluginagentmarketplace
Master Kubernetes storage management and networking architecture. Learn persistent storage, network policies, service discovery, and ingress routing.