agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/azure-dev/.github/skills/azd-preflight/SKILL.md

azd-preflight

Skill573 starsChanged 8 months agoMITView on GitHub

**WORKFLOW SKILL** — Runs `go tool 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.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every changed CHANGELOG.md passes its targeted spell check

    line 40
  2. Distinctive:

    All auto-applied fixes are saved to disk (not staged or committed — the user decides when to commit)

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

azd-preflight

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

Overview

The azd preflight suite (go tool mage preflight) validates code quality 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

  • go tool mage preflight exits successfully, or unresolved failures are clearly reported
  • Every changed CHANGELOG.md passes its targeted spell check
  • 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free