agentleFS
crgarcia12crgarcia12/Liliput/.github/skills/deploy-diagnostics/SKILL.md

deploy-diagnostics

Skill4 starsChanged 4 months agoISCView on GitHub

Diagnose and resolve Azure deployment failures by analyzing error output, checking Azure resource state, and suggesting fixes. Use when azd provision fails, azd deploy fails, smoke tests fail against live deployment, container images fail to push/pull, or any Phase 6 deployment error occurs. Trigger on deployment errors, infrastructure failures, or post-deploy smoke test failures.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Deploy Diagnostics

Diagnose and resolve Azure deployment failures.

Steps

  1. Parse error output — Identify the error type from AZD stdout/stderr
  2. Classify the error — Match against known patterns (see below)
  3. Check resource state — Verify Azure resource health if accessible
  4. Suggest fix — Provide specific remediation
  5. Verify fix — After applying, re-run the failed command

Known Failure Patterns

PatternSymptomFix
Quota exceededQuotaExceeded in errorChange region or request quota increase
Name conflictConflictError or DNS takenUse a different environmentName
Image pull failureImagePullBackOffVerify ACR push succeeded and identity has AcrPull role
Bicep validationInvalidTemplateCheck infra/main.bicep syntax and parameter values
Permission deniedAuthorizationFailedVerify subscription access and required RBAC roles
Region unavailableLocationNotAvailableForResourceTypeDeploy to a supported region

Diagnostic Commands

azd show                                                                    # deployment status
azd provision --debug                                                       # provisioning logs
az resource list --resource-group <rg-name> --output table                  # resource health
az containerapp logs show --name <app-name> --resource-group <rg-name>      # container app logs

Output Format

Error: <classification>
Root Cause: <description>
Fix: <specific action>
Confidence: HIGH | MEDIUM | LOW

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.