atmos-component-hygiene

Detect hygiene issues in Atmos Terraform components during creation and pull request review.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill atmos-component-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atmos-component-hygiene
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/atmos/hygiene
Command: npx skills add https://github.com/infraspecdev/tesseract --skill atmos-component-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill catches common Atmos Terraform component mistakes before they reach pull request review, reducing avoidable deployment failures, linting issues, and configuration drift.

Core Features & Use Cases

  • Repository-Level Validation: Checks ignore rules, terraform-docs setup, .tflint.hcl presence, and CI linting coverage.
  • Per-Component Review: Verifies versions constraints, baseline variables, documentation markers, and the absence of committed provider, backend, region, and account-id mistakes.
  • Practical Use Case: Use it after adding or changing an Atmos component to get a structured PASS or FAIL report with clear remediation guidance.

Quick Start

Use the atmos component hygiene skill to inspect this repository for Atmos Terraform component hygiene issues and report the findings in a pass or fail table.

Frequently Asked Questions about atmos-component-hygiene

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

FAQPage Schema
How do I check Atmos Terraform components for common configuration mistakes?

Terraform version constraints and baseline variables are validated per component to ensure they meet Atmos hygiene standards. This Skill checks for proper version pinning and required baseline variable definitions, reporting any missing or misconfigured elements in a PASS or FAIL table.

What happens if I accidentally commit provider, backend, region, or account-id details in Terraform components?

This Skill detects committed provider, backend, region, or account-id mistakes in Terraform components during review. It flags these hardcoded configuration details and provides remediation guidance to remove them before they cause deployment failures or configuration drift.

How do I validate terraform-docs markers and .tflint.hcl setup in an Atmos repository?

To validate terraform-docs markers and .tflint.hcl setup in an Atmos repository, this Skill performs repository-level validation. It checks for proper terraform-docs marker presence, .tflint.hcl configuration, and CI linting coverage across both single-component and multi-component Atmos repositories.

Can I use this Atmos component hygiene check on multi-component repositories?

Yes, you can use this Atmos component hygiene check on multi-component repositories. It applies to both single-component and multi-component Atmos repositories during component creation, modification, and pull request review, verifying gitignore rules, version constraints, and CI linting coverage.

When should I run an Atmos Terraform hygiene check during development?

You should run an Atmos Terraform hygiene check after adding or changing an Atmos component. This timing catches common mistakes like missing baseline variables or committed backend details early, reducing avoidable deployment failures and configuration drift before pull request review.