scaffold-service-deploy

To generate GitHub Actions workflows for AWS deployments, this Skill automates the creation of two-stage build and deploy pipelines with manual gates and per-environment approvals. It coordinates service and infrastructure repositories using workflow_dispatch events to ensure compliant releases.

OIDC-based authentication for GitHub Actions AWS deployments is a secure method that uses short-lived tokens instead of long-lived AWS credentials. This Skill enforces OIDC authentication within its generated workflows to prevent unauthorized access to your AWS infrastructure during deployments.

Yes, scaffold-service-deploy supports AWS Lambda, ECS Fargate, and App Runner targets within the infrastructure deployment plane. It pairs with a Terraform scaffold to generate the necessary environment checklists and deployment workflows for these compute targets.

No, you cannot deploy directly to production from the service repository using this workflow. The generated workflows enforce guardrails by requiring staging and production approvals, preventing direct production deployments and ensuring data integrity across environments.

Yes, you need an existing Terraform scaffold before generating service deployment workflows. The Skill requires this infrastructure scaffold to connect the service repository with the infrastructure repository, ensuring the generated GitHub Actions workflows dispatch correctly.

To automate multi-repo CI/CD pipelines linking service and infrastructure repositories, run the scaffold command to generate coordinating GitHub Actions workflows. These workflows use workflow_dispatch and OIDC authentication to enforce gated, compliant AWS deployments across both repositories.