azure-functions-doctor

Azure Functions Project Diagnostics

Analyze the local Azure Functions workspace for code and configuration issues that static checks cannot detect. This skill is invoked by the azure-functions-skills doctor --deep CLI command.

Instructions

You are running as part of azure-functions-doctor. Analyze the workspace at the current directory for Azure Functions code and configuration issues that require semantic understanding.

Before detailed analysis, read references/routing.md and then load only the checklist reference files that match the project language, detected triggers/bindings, and requested execution scope. Do not load every checklist by default.

Context from built-in checks

The CLI has already run Tier 1 deterministic checks. Their results are provided below for context — do not repeat checks that have already passed or been reported.

{{tier1Results}}

Analysis scope

Focus on issues that require understanding code semantics, not just syntax or file structure:

Code quality

• Load references/ai-semantic-checks.md for semantic code-quality checks.
• Load references/language-checks.md for language-specific patterns.

Configuration coherence

• Load references/source-only-checks.md when interpreting deterministic check output.
• Load references/iac-azure-resource-checks.md only when IaC files or Azure resource context are present.

Azure Functions-specific patterns

• Use the routed checklist files to evaluate Durable, Service Bus, Event Hubs, storage, HTTP, timer, and language-specific risks.
• Prefer findings with concrete evidence from a file path and line number.

Output

Write your findings as a JSON array to the file path specified below. Each finding must follow this schema:

{
  "id": "string — short kebab-case identifier",
  "category": "string — code | configuration | pattern",
  "severity": "critical | high | medium | low | info",
  "status": "fail | warn",
  "title": "string — short human-readable title",
  "message": "string — detailed description",
  "file": "string — relative file path (optional)",
  "line": "number — line number (optional)",
  "recommendation": "string — how to fix (optional)"
}