OpenParable
Skip to content
← Back to skills

Azd Preflight

Testing & Quality
azd-preflight

Azd Preflight is an Agent Skill for testing & quality published in the Azure/azure-dev repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

**WORKFLOW SKILL** — Runs `mage preflight` from `cli/azd/` and auto-fixes failures. Covers linting, formatting, copyright, spelling, build, and tests. Iterates fix-then-rerun cycles until all checks pass. INVOKES: mage CLI, go CLI, golangci-lint, cspell, bash/sh, ask_user. USE FOR: azd preflight, run preflight, preflight checks, pre-commit checks, azd lint, azd build and test, validate azd changes, check azd code quality, mage preflight. DO NOT USE FOR: deploying azd (use azure-deploy), changelog (use changelog-generation), creating PRs (use pull-request), running only unit tests without the full suite.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Azure/azure-dev/blob/HEAD/.github/skills/azd-preflight/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/azd-preflight, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

azd-preflight

Runs the full azd preflight suite and auto-fixes failures.

Overview

The azd preflight suite (mage preflight) validates code quality across 8 checks before changes are submitted. This skill runs the suite, parses failures, applies automated fixes, and re-runs until all checks pass — or escalates to the user when a fix requires human judgment.

{{ references/preflight-checks.md }}

{{ references/workflow.md }}

{{ references/output-and-errors.md }}

Exit Criteria

  • All 8 preflight checks pass (or user explicitly chose to skip specific checks)
  • All auto-applied fixes are saved to disk (not staged or committed — the user decides when to commit)
  • A clear summary of what passed, what was fixed, and what was skipped is displayed