azure-app-onboard-prereq

Overview

Azure App Onboard Prereq is a Claude Code skill that performs a thorough pre-deployment assessment of your source code before any Azure infrastructure work begins. It serves as Phase 1 of the Azure App Onboard pipeline (or can run standalone) and evaluates your repository across three axes: build health, application completeness, and Azure deployment feasibility. The evaluation is entirely read-only and static -- it never runs package installs, builds, or test suites. It produces structured artifacts including per-component verdicts (PASS, WARN, or FAIL), detected infrastructure patterns, and a readiness report that feeds into downstream architecture and deployment phases.

Key Features

• Three-axis evaluation covering build configuration health, application completeness, and deployability to Azure, each producing clear PASS/WARN/FAIL verdicts per component
• Strictly read-only analysis that never executes install, build, or test commands, ensuring no side effects on your repository during the assessment
• Automatic stack and component detection that scans for project manifests, Dockerfiles, and framework markers to identify your application stack and classify monorepo components
• Cloud SDK migration detection that flags AWS, GCP, or Firebase dependencies and routes to the appropriate migration workflow before proceeding
• Structured output artifacts including prereq-output.json, context.json updates, and a human-readable readiness report, enabling seamless handoff to the architecture planning phase
• Guided remediation protocol for any FAIL verdicts, with a consent-gated build validation step that only runs commands after explicit user approval

Who is this for?

• Developers who want to know if their codebase is ready for Azure before investing time in infrastructure planning
• Teams evaluating whether an existing application can be moved to Azure without major rewrites or dependency changes
• Engineers looking for a quick, non-destructive scan of deployment blockers such as missing configurations, incompatible frameworks, or unsupported dependencies
• DevOps practitioners who need a structured readiness report to share with stakeholders before kicking off a cloud migration project