oma-tf-infra

Designs, reviews, and validates Terraform infrastructure across AWS, GCP, Azure, and Oracle Cloud.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/javiruu/viru-air --skill oma-tf-infra-javiruu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oma-tf-infra
Source: https://github.com/javiruu/viru-air/tree/main/.agents/skills/oma-tf-infra
Command: npx skills add https://github.com/javiruu/viru-air --skill oma-tf-infra-javiruu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing and reviewing Terraform configurations across multiple cloud providers is error-prone: state mismanagement, over-privileged IAM, hardcoded secrets, and destructive plan changes can cause outages or security incidents. This Skill provides a structured workflow for designing, implementing, and reviewing multi-cloud infrastructure-as-code with built-in guardrails. ## Core Features & Use Cases - Multi-Cloud Provisioning: Generates provider-correct HCL for compute, databases, storage, networking, IAM, and CDN across AWS, GCP, Azure, and Oracle Cloud, with a resource mapping table between providers. - Plan Review & Risk Analysis: Analyzes terraform plan output, flags destructive changes, and enforces validation steps (fmt, validate, plan, Checkov/tfsec scans) before any apply. - Governance & Cost Controls: Includes policy-as-code examples (OPA, Sentinel), Terratest patterns, cost optimization strategies (spot instances, lifecycle rules, autoscaling schedules), and ISO/IEC 42001, ISO 22301, and ISO/IEC/IEEE 42010 infrastructure guidance. - Use Case: A team migrating a manually configured GCP environment to Terraform uses this Skill to detect the provider, design remote state with locking, write modular HCL with OIDC-based CI/CD authentication, and review the plan for destructive risks before applying. ## Quick Start Ask the agent to design a Terraform configuration for deploying a containerized API with a managed database on your cloud provider, including remote state, least-privilege IAM, and a plan review before apply.

Frequently Asked Questions about oma-tf-infra

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a terraform plan before applying?▼

Run terraform fmt, validate, and plan, then examine the add/change/destroy counts. Flag any destroy or recreate actions on stateful resources like databases, verify backups and rollback plans, and run Checkov or tfsec scans before approving the apply.

How do I set up OIDC authentication for GitHub Actions with Terraform?▼

Create an OIDC identity provider resource for your cloud (aws_iam_openid_connect_provider, google_iam_workload_identity_pool, or Azure federated credentials), then define a role with a trust policy scoped to your repository and branch. This avoids long-lived access keys in CI/CD.

Does this Terraform workflow support multiple cloud providers?▼

Yes, it covers AWS, GCP, Azure, and Oracle Cloud with provider detection from existing HCL and a resource mapping table. Equivalent services like ECS Fargate, Cloud Run, Container Apps, and OCI Container Instances are mapped for multi-cloud design.

Why does terraform plan show unexpected changes on existing resources?▼

This indicates drift between state and real infrastructure, usually from manual console changes. Run terraform refresh to sync state, then decide whether to import the manual change into configuration or revert it.

When should I not use Terraform for a task?▼

Terraform is not suited for database schema design, query tuning, backend API implementation, or non-infrastructure CI/CD pipeline code. It also should never apply or destroy production infrastructure without explicit confirmation and backup awareness.

How do I reduce cloud costs with Terraform?▼

Use environment-based sizing with smaller instances for dev and staging, spot or preemptible instances for fault-tolerant workloads, autoscaling schedules for off-hours, and storage lifecycle rules that transition data to cheaper tiers. Tag all resources for cost allocation tracking.