neo-azure-pipelineslisted

# Azure Pipeline Script Design Specifications ## Perceive 1. When version-specific syntax or task versions matter, verify them against `https://learn.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops`; if browsing is unavailable, state the uncertainty and rely on bundled templates plus project evidence. 2. Identify the application's development language (e.g., .NET, Java, Python, Node.js) and its specific version requirements. 3. Identify the target deployment platform (e.g., Azure App Service, Azure Kubernetes Service, Function App, or on-premises servers). 4. Detect the project source code structure to confirm build tools (e.g., Maven, Gradle, Npm, NuGet) and testing frameworks. 5. Read security and compliance requirements, including Static Application Security Testing (SAST), package vulnerability scanning, and container image scanning. 6. Confirm environment variable requirements, secret information sources (e.g., Azure Key Vault), and Service Connection permissions. 7. **Proactively scan the `skills/neo-azure-pipelines/templates/` directory to identify existing reusable template resources. Includes:** * **Build**: `build/build-dotnet.yml` * **Deploy**: `deploy/deploy-app-service.yml`, `deploy/deploy-iis.yml` * **Utils**: `util/clean-artifact.yml`, `util/extract-artifact.yml`, `util/iis/*.yml`, etc. ## Reason 1. Compare documented task versions with existing configurations to determine if task versions need updating (e.g., using Checkout@v1