Skip to main content

eks-automode-maintain

A Claude Code skill for maintainers of this repository who need to keep code, templates, and documentation in sync.

When to use

Trigger this skill when you:

  • Changed a .tpl file and need to know what else to update
  • Want to verify 5-layer tagging consistency
  • Are preparing a PR and need the checklist
  • Need to update TAGGING.md or CLEANUP.md
  • Want to understand the file dependency graph

What it covers

The rendering chain

nodepool-templates/*.yaml.tpl (source of truth)
|
v terraform apply (templatefile + local_file)
|
nodepools/*.yaml (rendered output)

Key gotcha: editing a .tpl does NOT reach the cluster until terraform apply re-renders. kubectl apply of stale rendered YAML silently reverts the fix.

Decision matrix

ChangedAlso update
nodepool-templates/*.yaml.tplterraform apply to re-render; verify nodepools/
terraform/variables.tf (new var)setup.tf (pass to templatefile); README variable table
terraform/eks.tfclaude-md/TAGGING.md if tag-related; README if feature-facing
examples/* (new example)README examples table; docs site sidebar; setup.tf if .tpl
terraform/tagging.tfclaude-md/TAGGING.md; verify 5-layer coverage
scripts/cleanup.shclaude-md/CLEANUP.md flags/usage section
terraform/versions.tfREADME prerequisites (provider versions)
terraform/ingressclass.tfclaude-md/TAGGING.md Layer 5 section

5-layer tagging verification

LayerFileTags
1. Provider default_tagsterraform/main.tfAll TF-direct resources
2. cluster_tagsterraform/eks.tfEKS primary security group
3. NodeClass spec.tagsnodepool-templates/*.yaml.tplEC2, root EBS, ENIs
4. StorageClass tagSpecificationterraform/tagging.tfPVC-provisioned EBS
5. IngressClassParams spec.tagsterraform/ingressclass.tfALBs, target groups

PR checklist

  • Every .tpl change validated via terraform apply
  • New variables in README Configuration section
  • Tag changes reflected in claude-md/TAGGING.md
  • Cleanup changes reflected in claude-md/CLEANUP.md
  • New examples have README with prereqs and commands
  • Rendered YAML paths in .gitignore if generated
  • No hardcoded cluster names or account IDs
  • Example READMEs use relative paths

Reference docs (loaded on demand)

  • references/file-relationships.md -- complete file map and dependency graph
  • references/tagging-consistency.md -- full 5-layer verification with debug commands
  • references/docs-sync-checklist.md -- when to update each doc file, PR template

Sources