Common Legacy Non Sdk Custom Code Generation

Azure/azure-cli/.github/skills/common-legacy-non-sdk-custom-code-generation

Azure· v1.0.0

codingResmi

Resmi Sağlayıcı Skill'iView repo

Use after routing to legacy non-SDK custom, or when adding/updating Azure CLI legacy custom command functions whose main behavior is local tools, subprocesses, data-plane APIs, raw HTTP, diagnostics, install flows, file/environment orchestration, or generated AAZ commands used only as helpers.

Dosyalar1 dosya

SKILL.md244 satır

Loading editor…

Kurulum

Önerilen

Tek komut — ajanınız otomatik olarak devreye alır.

AI aracını seç

Kurulum komutunu görmek için yukarıdan bir AI aracı seçin.

veya

Manuel Kurulum

Daha fazla adım

Dosyayı indirin ve ajanınızın sistem istemine yapıştırın.

Skill detayları

Versiyonv1.0.0

YazarAzure

Kategoricoding

Skill IDAzure/azure-cli/.github/skills/common-legacy-non-sdk-custom-code-generation

İlgili skill'ler

Common Aaz Custom Code GenerationUse after routing to AAZ subclass custom, or when adding/updating Azure CLI AAZ generated command customization. Generates custom classes that subclass AAZ generated commands while limiting uncertainty with required slots, templates, and validation gates.Common Custom Code RouterUse when adding or updating Azure CLI command module custom code and deciding whether the requested work should use AAZ subclass custom, legacy SDK-backed custom, or legacy non-SDK custom before generating code.Common Legacy Sdk Backed Custom Code GenerationUse after routing to legacy SDK-backed custom, or when adding/updating Azure CLI legacy custom command functions that call Azure Python SDK clients through CliCommandType, client_factory, cmd.get_models, g.command, g.show_command, or generic_update_command.Common Live Test From HelpUse when creating or updating Azure CLI live tests from module help examples. Resolve generated vs manual help precedence, detect missing examples, scaffold scenario tests, and enforce 80% command-level coverage checks.Openspec Apply ChangeImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.Openspec Archive ChangeArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.