terraform-deployer

Featured

Deploy infrastructure using Terraform

DevOps & Infrastructure 16,931 stars 1442 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Terraform Deployer ## Purpose Runs Terraform commands to manage cloud infrastructure. Only activates for explicit Terraform CLI operations. ## Triggers Activates on: - "run terraform plan" - "terraform apply" - "deploy infrastructure with terraform" Does NOT activate on: - General deployment requests without mentioning Terraform - "plan" used in non-infrastructure contexts - "deploy" without infrastructure/Terraform context ## Usage Provide a Terraform workspace path and the desired command (plan, apply, destroy).

Details

Author: NVIDIA
Repository: NVIDIA/SkillSpector
Created: 5 months ago
Last Updated: today
Language: Python
License: Apache-2.0

Integrates with

Terraform · Infrastructure

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Listed

deploy

Deploy the current project using its own infrastructure. Detects OpenTofu configs, Dockerfile, and release steps, then applies them safely.

1 Updated 2 weeks ago

samuel-stidham

AI & Automation Listed

project-deploy

Use when deploying to production, running terraform apply against the App Platform app, verifying what version is live, or diagnosing a deploy that appears to have succeeded and changed nothing.

2 Updated today

ubermuda

DevOps & Infrastructure Listed

terraform-k8s

Author and operate infrastructure-as-code with Terraform/OpenTofu and Kubernetes manifests — declarative provisioning, state management, modules, plan/apply discipline, and the K8s object model (Deployment/Service/Ingress, probes, requests/limits, HPA, ConfigMap/Secret, RBAC). Use when writing a Terraform module, structuring remote state and workspaces, debugging drift or a destructive plan, writing or reviewing K8s YAML/Helm/Kustomize, sizing requests/limits, or wiring probes. Boundary vs deployment-cicd — deployment-cicd owns the release process (CI pipeline, build/test stages, blue-green/canary/rolling rollout, version tagging, rollback playbook); this skill owns the substrate those releases deploy onto — declarative provisioning of cloud resources and the Kubernetes object definitions themselves. The pipeline runs apply; this skill is what those files contain. Defers image-build craft to docker and host-level tuning to linux-sysadmin.

6 Updated yesterday

kouroshez