Agent skill · software engineering · github
azure-deployment-preflight
Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks. Use this skill before any deployment to Azure to preview changes, identify potential issues, and ensure the deployment will succeed. Activate when users mention deploying to Azure, validating Bicep files, checking deployment permissions, previewing infrastructure changes, running what-if, or preparing for azd provision.
Why this skill is useful
Adds specific commands and validation processes for Bicep deployments that the AI wouldn't reliably generate on its own.
What it needs
Requires azure-cli, bicep installed locally. Requires azure account access. About 4k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Azure Deployment Preflight Validation This skill validates Bicep deployments before execution, supporting both Azure CLI (az) and Azure Developer CLI (azd) workflows. When to Use This Skill Before deploying infrastructure to Azure When preparing or reviewing Bicep files To preview what changes a deployment will make To verify permissions are sufficient for deployment Before running azd up, azd provision, or az deployment commands Validation Process Follow these steps in order. Continue to the next step even if a previous step fails—capture all issues in the final report. Step 1: Detect Project Type Determine the deployment workflow by checking for project indicators: 1. Check for azd project: Look for azure.yaml in the project root If found → Use azd workflow If not found → Use az CLI workflow 2. Locate Bicep files: Find all .bicep files to validate For azd projects: Check infra/ directory first, then project root For standalone: Use the file specified by the user or search common locations (infra/, deploy/, project root) 3. Auto-detect parameter files: For each Bicep file, look for matching parameter files: <filename>.bicepparam (Bicep parameters - preferred) <filename>.parameters.json (JSON parameters) parameters.json or parameters/<env>.json in same directory Step 2: Validate Bicep Syntax Run Bicep CLI to check template syntax before attempting deployment validation: What to capture: Syntax errors with line/column numbers Warning messages Build success/failure status If Bicep CLI is not installed: Note the issue in the report Continue to Step 3 (Azure will validate syntax during what-if) Step 3: Run Preflight Validation Choose the appropriate validation based on project type detected in Step 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/azure-deployment-preflight