What problem does it solve?
Deployment pipelines fail for many reasons—Terraform state locks, Azure OIDC authorization errors, drift between configuration and cloud resources, failing migration jobs, or quota limits—and finding the root cause is slow and error-prone. This Skill provides a structured diagnostic workflow for the deploy.yml GitHub Actions pipeline so failures are resolved from evidence rather than guesswork.
Core Features & Use Cases
- Failed Run Inspection: Uses
gh run list and gh run view --log-failed to gather evidence from the failing step before any code or infrastructure change.
- Targeted Diagnostic Paths: Covers Terraform locks, Azure/OIDC authorization and RBAC, configuration drift, Container Apps migration jobs, failing tests, and Azure quota or platform issues.
- Safe Remediation Guardrails: Requires explicit confirmation before force-unlocking state, applying Terraform, mutating state, or changing production access.
- Use Case: A deploy.yml run fails with a Terraform state lock error. The Skill guides you to identify the lock owner and active workflows, confirm the lock is stale with the user, and only then unlock the exact lock ID.
Quick Start
Ask the assistant to diagnose why the latest deploy.yml GitHub Actions run failed and identify the root cause.