agentleFS
selamy-labsselamy-labs/agent-skills/skills/iac-not-ad-hoc/SKILL.md

iac-not-ad-hoc

Skill0 starsChanged 7 days agoMITView on GitHub

Use for infrastructure, repository settings, cloud resources, Kubernetes, runner, secret, cron, runtime config, or deployment changes. Requires a declarative source of truth.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the declarative route is blocked, escalate the specific blocker and keep the system's status explicit.

    line 27
  2. Distinctive:

    Use secret-manager and ExternalSecret-style sync paths for secrets.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

IaC, Not Ad Hoc

Infrastructure and runtime configuration must be reproducible from source.

Required Path

  • Repository settings: manage through an infrastructure provider where possible.
  • Cloud resources and IAM: declare in infrastructure as code with keyless auth where possible.
  • Kubernetes/runtime: use manifests, charts, and GitOps rather than live edits.
  • Secrets: use the established secret manager and sync mechanism. Never put credentials in chat or repositories.
  • Cron/config: commit it to the service or agent repository, not a live pod.

Manual mutation is not an implementation path. During incidents, use live commands for read-only diagnosis, imports, plans, and verification; make the state-changing fix through the declared source of truth. If a resource already exists because someone created it by hand, import it into the declarative state instead of leaving it unmanaged or destroying and recreating it for tidiness.

If the declarative route is blocked, escalate the specific blocker and keep the system's status explicit. Do not bridge the gap with an untracked live edit.

Incident Bar

  • Merge GitOps or IaC changes; do not point live controllers at a temporary branch.
  • Use secret-manager and ExternalSecret-style sync paths for secrets; do not create live Kubernetes secrets by hand.
  • End-state test: a clean apply or sync from the declared source recreates the required stack without hidden manual steps.

Module Structure (Terraform / OpenTofu)

For Terraform/OpenTofu module file layout, see the terraform-module-layout skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.