Harness-engineering harness-infrastructure-as-code

name: harness-infrastructure-as-code

install
source · Clone the upstream repo
git clone https://github.com/Intense-Visions/harness-engineering
manifest: agents/skills/claude-code/harness-infrastructure-as-code/skill.yaml
source content

name: harness-infrastructure-as-code version: "1.0.0" description: Terraform, CloudFormation, Pulumi patterns and IaC best practices stability: static cognitive_mode: advisory-guide tier: 3 internal: false keywords:

  • Terraform
  • CloudFormation
  • Pulumi
  • IaC
  • infrastructure
  • HCL
  • CDK
  • AWS
  • GCP
  • Azure
  • state
  • module
  • provider
  • resource stack_signals:
  • "*.tf"
  • "terraform/"
  • "cloudformation/"
  • "*.template.yaml"
  • "*.template.json"
  • "Pulumi.yaml"
  • "cdk.json"
  • "infrastructure/" paths:
  • '*.tf'
  • '*.tfvars'
  • 'Pulumi.yaml'
  • 'cdk.json'
  • '*.template.yaml'
  • '*.template.json' triggers:
  • manual
  • on_new_feature
  • on_pr platforms:
  • claude-code
  • gemini-cli
  • cursor
  • codex tools:
  • Bash
  • Read
  • Write
  • Edit
  • Glob
  • Grep
  • emit_interaction cli: command: harness skill run harness-infrastructure-as-code args:
    • name: path description: Project root path required: false
    • name: provider description: Cloud provider context (aws, gcp, azure) required: false
    • name: tool description: IaC tool to focus on (terraform, cloudformation, pulumi, cdk) required: false mcp: tool: run_skill input: skill: harness-infrastructure-as-code path: string type: rigid phases:
  • name: detect description: Identify IaC tool, provider, and module structure required: true
  • name: analyze description: Evaluate resource definitions, state management, and module patterns required: true
  • name: design description: Recommend module decomposition, naming, and drift prevention required: true
  • name: validate description: Verify configuration correctness and security posture required: true state: persistent: false files: [] depends_on: []