Validates Terraform wiring and CI/CD workflow coverage when adding new project resources.

Install

mkdir -p .claude/skills/cicd && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18168" && unzip -o skill.zip -d .claude/skills/cicd && rm skill.zip

Installs to .claude/skills/cicd

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Run after adding a new resource, Lambda function, or project to verify Terraform wiring is complete and GitHub Actions workflows cover the new component.
153 chars · catalog descriptionno explicit “when” trigger
Intermediate

Key capabilities

  • Identify new resources or functions from the current diff
  • Verify Terraform wiring for new Lambda functions (resource, log group, permissions)
  • Check IAM role and policy for least-privilege actions
  • Ensure new input values are declared as variables in `variables.tf`
  • Verify GitHub Actions workflows include the new project directory
  • Check GitHub Actions for AWS credentials usage and environment protection

How it works

The skill identifies new components from the current diff, then performs checks on Terraform files and GitHub Actions workflows to ensure correct wiring and coverage.

Inputs & outputs

You give it
A new Lambda function, Terraform resource, or project directory
You get back
A CI/CD check report detailing findings and next steps

When to use cicd

  • Verifying new Lambda infrastructure
  • Auditing Terraform resource wiring
  • Checking CI/CD workflow completeness

About this skill

CI/CD Check

Run after adding a new resource, Lambda function, or project to verify Terraform wiring is complete and GitHub Actions workflows cover the new component.

How to use

Type /cicd after adding any new Lambda function, Terraform resource, or project directory.

Steps

  1. Identify the new resource or function from the current diff.
  2. Run Part 1 (Terraform wiring) against the relevant project's Terraform files.
  3. Run Part 2 (GitHub Actions) against .github/workflows/.
  4. Report findings using the output format.

Part 1 — Terraform wiring

For each new Lambda function:

  • aws_lambda_function resource present in main.tf
  • aws_cloudwatch_log_group for the function in main.tf (retention_in_days set)
  • aws_lambda_permission for the trigger (S3, API Gateway, or EventBridge) in main.tf
  • IAM role and policy in iam.tf — least-privilege actions only
  • New input values declared as variables in variables.tf (not hardcoded in main.tf)
  • Endpoint URL or function ARN exported in outputs.tf

For each new project directory:

  • backend.tf present pointing to bootstrap S3 bucket with unique key (p[N]/terraform.tfstate)
  • terraform.tfvars present (gitignored) with suffix and alert_email filled in
  • variables.tf declares aws_region, project_name, suffix, common_tags at minimum

Part 2 — GitHub Actions

  • .github/workflows/terraform-init.yml (or equivalent) includes the new project directory
  • Workflow does not hardcode AWS credentials — uses ${{ secrets.AWS_ACCESS_KEY_ID }} pattern
  • Workflow references the correct relative path to the project directory
  • No new workflow file introduces a pull_request trigger without environment protection

Output format

## /cicd — YYYY-MM-DD

### Findings
[MISSING] project5-document-engine/outputs.tf — query API endpoint URL not exported
[WARN]    .github/workflows/terraform-init.yml:12 — project5 directory not in matrix
[OK]      project5-document-engine/backend.tf — remote state backend present and correctly keyed

### Summary
1 MISSING and 1 WARN to address before deploy.

### Next step
Add query_api_endpoint output to project5-document-engine/outputs.tf, then add
project5-document-engine to the workflow matrix at .github/workflows/terraform-init.yml:12.

If no findings: write No findings — all checks pass. under Findings.

When not to use it

  • When the user is not adding a new resource, Lambda function, or project
  • When the user is not verifying Terraform wiring
  • When the user is not checking GitHub Actions workflows

Limitations

  • Checks are specific to `aws_lambda_function`, `aws_cloudwatch_log_group`, `aws_lambda_permission`
  • Focuses on `backend.tf`, `terraform.tfvars`, `variables.tf`, `outputs.tf` for Terraform
  • GitHub Actions checks are specific to `terraform-init.yml` and credential patterns

How it compares

This skill automates a structured CI/CD check for new components, ensuring adherence to Terraform and GitHub Actions best practices, which is more consistent and thorough than a manual review.

Compared to similar skills

cicd side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
cicd (this skill)01moNo flagsIntermediate
devops-iac-engineer27moReviewAdvanced
aws-solution-architect202moReviewAdvanced
terraform-module-library74moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

devops-iac-engineer

davila7

Implements infrastructure as code using Terraform, Kubernetes, and cloud platforms. Designs scalable architectures, CI/CD pipelines, and observability solutions. Provides security-first DevOps practices and site reliability engineering guidance.

223

aws-solution-architect

alirezarezvani

Design AWS architectures for startups using serverless patterns and IaC templates. Use when asked to design serverless architecture, create CloudFormation templates, optimize AWS costs, set up CI/CD pipelines, or migrate to AWS. Covers Lambda, API Gateway, DynamoDB, ECS, Aurora, and cost optimization.

2047

terraform-module-library

wshobson

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

759

aws-advisor

tech-leads-club

Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service.

529

hybrid-cloud-networking

wshobson

Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking.

310

genkit-infra-expert

jeremylongshore

Execute use when deploying Genkit applications to production with Terraform. Trigger with phrases like "deploy genkit terraform", "provision genkit infrastructure", "firebase functions terraform", "cloud run deployment", or "genkit production infrastructure". Provisions Firebase Functions, Cloud Run services, GKE clusters, monitoring dashboards, and CI/CD for AI workflows.

15

Search skills

Search the agent skills registry