Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
julianobarbosa avatar

Managing Infra

  • 100 installs
  • 6 repo stars
  • Updated July 22, 2026
  • julianobarbosa/claude-code-skills

Best practices for managing infrastructure and operations.

About

Infrastructure patterns for Kubernetes, Terraform, Helm, Kustomize, and GitHub Actions. Use when making K8s architectural decisions.

  • CI workflow: Lint, test, compile on PRs
  • Release workflow: Multi-arch Docker build on tags

Managing Infra by the numbers

  • 100 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #814 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/julianobarbosa/claude-code-skills --skill managing-infra

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs100
repo stars6
Last updatedJuly 22, 2026
Repositoryjulianobarbosa/claude-code-skills

What it does

Best practices for managing infrastructure and operations.

Files

SKILL.mdMarkdownGitHub ↗

Infrastructure Patterns

When to Use What

ToolUse For
Raw K8s YAMLSimple deployments, one-off resources
KustomizeEnvironment variations, overlays without templating
HelmComplex apps, third-party charts, heavy templating
TerraformCloud resources, infrastructure lifecycle
GitHub ActionsCI/CD, automated testing, releases
MakefileBuild automation, self-documenting targets
DockerfileContainer builds, multi-stage, multi-arch

Quick Decisions

Kustomize when: Simple env differences, readable manifests, patching YAML Helm when: Complex templating, third-party charts, release management

K8s Security Defaults

Every workload: non-root user, read-only filesystem, no privilege escalation, dropped capabilities, network policies.

GitHub Actions Patterns

  • CI workflow: Lint, test, compile on PRs (run on both x86 + ARM)
  • Release workflow: Multi-arch Docker build on tags (native ARM runners)
  • Pin actions by SHA, least-privilege permissions

References

  • KUBERNETES.md - K8s resource patterns
  • TERRAFORM.md - Terraform module patterns
  • GITHUB-ACTIONS.md - CI/CD workflow patterns
  • MAKEFILE.md - Build automation patterns
  • DOCKERFILE.md - Container build patterns
  • templates/ - Ready-to-use templates

Commands

kubectl apply -k ./              # Apply kustomize
helm upgrade --install NAME .    # Install/upgrade chart
terraform plan && terraform apply

---

Gotchas

  • Terraform state lock contention: default 10-min lock timeout; bumped timeout doesn't help if the lock holder hung — force-unlock only after confirming the process is dead.
  • Helm release name reuse on uninstalled-but-not-purged release fails install with "already exists" — use --no-hooks + explicit purge, or never reuse names.
  • Kustomize patches that match nothing silently produce empty diffs — verify with kustomize build after every patch addition.
  • Terraform `for_each` over a computed value forces apply-time count — can cause spurious re-creation of resources between plans.
  • `helm upgrade --install` on a changed values schema can silently drop fields that no longer match — diff the rendered output, not just the values file.
  • `kubectl apply --server-side` vs client-side conflicts when both have been used: client-side last-applied-config can shadow server-side managed fields without error.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.