Skip to main content

azure-validate

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), permissions, and prerequisites before deploying. WHEN: validate my app, check d...

Informations de source

Dépôt
GrayCodeAI/starling
Dernière activité de la source
13 juillet 2026 à 09:28
Langue détectée de SKILL.md
anglais
Étoiles
2
Forks
0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
azure-validate
description
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), permissions, and prerequisites before deploying. WHEN: validate my app, check d...
license
MIT
tags
["aws"]
metadata
None
author
Microsoft
version
1.0.0
# Azure Validate > **AUTHORITATIVE GUIDANCE** — Follow these instructions exactly. This supersedes prior training. > **⛔ STOP — PREREQUISITE CHECK REQUIRED** > > Before proceeding, verify this prerequisite is met: > > **azure-prepare** was invoked and completed → `.azure/plan.md` exists with status `Approved` or later > > If the plan is missing, **STOP IMMEDIATELY** and invoke **azure-prepare** first. > > The complete workflow ensures success: > > `azure-prepare` → `azure-validate` → `azure-deploy` ## Triggers - Check if app is ready to deploy - Validate azure.yaml or Bicep - Run preflight checks - Troubleshoot deployment errors ## Rules 1. Run after azure-prepare, before azure-deploy 2. All checks must pass—do not deploy with failures 3. ⛔ **Destructive actions require `ask_user`** — global-rules ## Steps | # | Action | Reference | |---|--------|-----------| | 1 | **Load Plan** — Read `.azure/plan.md` for recipe and configuration. If missing → run azure-prepare first | `.azure/plan.md` | | 2 | **Run Validation** — Execute recipe-specific validation commands | recipes/README.md | | 3 | **Build Verification** — Build the project and fix any errors before proceeding | See recipe | | 4 | **Record Proof** — Populate **Section 7: Validation Proof** with commands run and results | `.azure/plan.md` | | 5 | **Resolve Errors** — Fix failures before proceeding | See recipe's `errors.md` | | 6 | **Update Status** — Only after ALL checks pass, set status to `Validated` | `.azure/plan.md` | | 7 | **Deploy** — Invoke **azure-deploy** skill | — | > **⛔ VALIDATION AUTHORITY** > > This skill is the **ONLY** authorized way to set plan status to `Validated`. You MUST: > 1. Run actual validation commands (azd provision --preview, bicep build, terraform validate, etc.) > 2. Populate **Section 7: Validation Proof** with the commands you ran and their results > 3. Only then set status to `Validated` > > Do NOT set status to `Validated` without running checks and recording proof. --- > **⚠️ MANDATORY NEXT STEP — DO NOT SKIP** > > After ALL validations pass, you **MUST** invoke **azure-deploy** to execute the deployment. Do NOT attempt to run `azd up`, `azd deploy`, or any deployment commands directly. Let azure-deploy handle execution. > > If any validation failed, fix the issues and re-run azure-validate before proceeding.
Voir sur GitHub