Terminal
Terminal/Skill
Diagnoses and fixes Azure Functions problems such as deployment failures, runtime errors, and trigger or binding failures, using logs and telemetry.
By Microsoft
Works with
npx skills add azure/azure-functions-skills --skill azure-functions-diagnosticsUse this skill to diagnose and resolve Azure Functions issues by orchestrating focused skills and loading only the references needed for the current app.
Write final answers in the user's language.
Do not load all diagnostic references up front. First collect the app inventory, infer runtime/language and trigger/binding/extension shape, then load only the matching language and extension reference files.
For multi-step reviews, source investigations, or remediation work, create a short checklist plan file or todo list and update it after each completed step. Do not require a checklist for quick read-only diagnosis because it adds token overhead.
Ask only for missing inputs needed to start:
24h for current or recent production issues.If the user has a local workspace issue without a deployed app, skip Azure resource collection and start from local project/runtime/trigger discovery.
Follow workflow.md. Use shared reference routing from ../azure-functions-common/references/routing.md only after inventory/health data identifies the relevant runtime, trigger, binding, or symptom.
Fast path:
azure-functions-inventory to collect static app specifications.azure-functions-health-status to collect current health, metrics, telemetry, and Activity Log.Use azure-functions-common for shared runtime, language, and trigger/binding references.
azure-functions-inventory if the app shape or configuration changed during remediation.azure-functions-health-status to re-check current health and telemetry before continuing diagnosis.Use this concise structure unless the user asks for a different format:
Target: <app/resource/local project>
Symptom: <summary>
Inventory: <runtime/plan/network/triggers summary>
Health: <current state/metrics/log findings summary>
Relevant references loaded: <language refs>, <extension refs>
Findings: <evidence-backed bullets>
Likely cause: <confirmed or suspected>
Recommended actions: <ordered steps>
Validation plan: <local/E2E/Azure validation steps>
Gaps: <missing permissions/telemetry/context>