Skip to content

Expecho/Agent42 / .claude/skills/deploy

Deploy Agent42 to Azure — explain, trigger, or monitor the GitHub Actions "Deploy" workflow (preflight → shared infra → build → ACR → Bicep).

Deploy Agent42

Deployment is fully owned by .github/workflows/deploy.yml (workflow name: Deploy). There is no manual deploy path — never run az deployment group create or docker push by hand against production.

How it deploys

  1. Trigger: push to main touching src/**, infra/**, Directory.Packages.props, .dockerignore, or the workflow file — or a manual workflow_dispatch. Merging a PR into main is the normal deploy, but a PR touching none of those paths does NOT deploy.
  2. preflight: fails closed when a repository variable is missing or would change what is deployed (an absent variable expands to an empty string; a missing custom domain would unbind the live one).
  3. build-and-push: deploys infra/shared.bicep (registry and Container Apps environment, reused or created), builds src/Agent42.Backend/Dockerfile, tags with the first 12 chars of the SHA, pushes to the ACR.
  4. deploy: az deployment group create of infra/main.bicep into the resource group. The registry, environment, resource group, domain and Cosmos region come from repo variables (ADR 0128); they are documented in docs/features/azure-deployment.md and set in the repository's Actions variables. Quirks are in .agentic/gotchas.md — read those entries before changing anything in this pipeline.

Commands

IntentCommand
Status of latest deploygh run list --workflow Deploy --limit 5
Trigger manuallygh workflow run Deploy (then gh run watch)
Watch a running deploygh run watch
Logs of a failed deploygh run view <run-id> --log-failed

Guardrails

  • IAM/RBAC failures in the deploy: per CLAUDE.md hard rule 5, never fix by running role-assignment writes yourself — prepare the exact command and hand it to the user.
  • If the deploy unbinds the custom domain, the managed certificate name drifted — see the "Custom domain must stay declared in Bicep" gotcha.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall