gate-iac

Deploys the IAC-001 control wiring Terraform static analysis into pre-commit hooks and CI workflows.

1|Updated Aug 16, 2026
One-click install
npx skills add https://github.com/Eaiger-Ent/ee-standard --skill gate-iac-eaiger-ent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gate-iac
Source: https://github.com/Eaiger-Ent/ee-standard/tree/main/plugins/control-register/skills/gate-iac
Command: npx skills add https://github.com/Eaiger-Ent/ee-standard --skill gate-iac-eaiger-ent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories often declare that infrastructure code must be statically analysed, yet the analysers are unpinned, wired inconsistently between pre-commit and CI, or not enforced as required checks. This Skill deploys the IAC-001 control from a controls.yaml register so that checkov and tflint run identically at commit time and in CI, with every value derived from the register rather than chosen ad hoc. ## Core Features & Use Cases - Register-driven deployment: Reads analysers, arguments, tool invocation, and suppression rules from controls.yaml so no tool or version is hard-coded in the skill. - Dual-locus wiring: Writes a stamped pre-commit hook and, only when no full audit exists, a CI step that runs register-check against IAC-001. - Self-verification: Runs register-check run --control IAC-001 after deployment and reports the verdict as given, distinguishing failed deployments from real Terraform findings. - Use Case: A team adopting the ee-standard register in a repository containing Terraform invokes the skill to wire checkov and tflint into .pre-commit-config.yaml and their gating workflow, then receives an honest report including UNCLASSIFIED verdicts when analysers are not yet pinned. ## Quick Start Ask the AI to deploy gate-iac into the current repository using its controls.yaml register and report the verification verdict.

Frequently Asked Questions about gate-iac

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

FAQPage Schema
How do I deploy Terraform static analysis into pre-commit and CI?▼

Invoke the gate-iac skill against a repository containing a controls.yaml register. It reads the analysers IAC-001 names, writes a stamped pre-commit hook and CI step running register-check, then verifies the deployment with the same checker that audits the repository.

What tools does IAC-001 use for Terraform analysis?▼

IAC-001's verify blocks run checkov with --directory . --compact --quiet and tflint with --recursive. One hook runs the control and the control runs both analysers, so the two can never drift into different definitions of what analysed means.

Can I deploy this gate in a repository without Terraform files?▼

No. The skill stops when no tracked *.tf or *.tfvars files exist, because IAC-001's predicate is evaluated against files and never self-declared. A hook for infrastructure that does not exist can only ever be noise.

Why does the deployment report UNCLASSIFIED instead of PASS?▼

UNCLASSIFIED means the register names an analyser it does not pin, so the control cannot be verified. The skill deliberately does not install unpinned tools; closing it requires a tools.checkov and tools.tflint entry in the repository's own register.

Does a failing checkov or tflint block mean the deployment failed?▼

No. A failing analyser block is a successful deployment finding real problems in the repository's Terraform. Only failing wiring or provenance stamp blocks indicate a failed deployment, and the skill reports which case occurred.

Should I keep tfsec or terrascan alongside checkov?▼

A second analyser is not a violation, but two analysers mean two suppression files and only one is checked by this standard. The skill shows what each legacy tool is configured to do and asks whether to remove it.