Stats
Actions
Tags
From infra-ops
Philosophy and practices for ensuring all infrastructure changes are codified, reproducible, and validated. Use when making infrastructure changes, deploying services, or reviewing operational procedures.
How this skill is triggered — by the user, by Claude, or both
Slash command
/infra-ops:repeatable-deploymentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**All infrastructure changes MUST be codified in the repository.** Manual changes to servers are temporary fixes that will be lost on redeployment. If you make a manual change to fix something, you MUST then codify it.
All infrastructure changes MUST be codified in the repository. Manual changes to servers are temporary fixes that will be lost on redeployment. If you make a manual change to fix something, you MUST then codify it.
Configuration files - Any config files placed on servers (model configs, app configs, etc.)
Environment variables - All env vars in compose templates, secrets via secret management lookups
Directory structure - Any directories that must exist on target hosts
External dependencies - Backends, plugins, or binaries extracted from images
Permissions - File/directory permissions that differ from defaults
mode, owner, group in automation tasksdocker exec to modify container stateWork is NOT complete until it can be reproduced from scratch. Manual fixes during debugging are acceptable, but the final deliverable must be validated by:
This ensures:
Exception: Quick debugging sessions may skip validation, but must create a follow-up issue to codify and validate the fix properly.
npx claudepluginhub code0100fun/botfiles --plugin infra-opsInfrastructure engineering discipline: infrastructure-as-code principles, deliverable quality standards, environment parity, change management, security posture, observability, incident response, policy-as-code, supply chain integrity, and disaster recovery. Invoke whenever task involves any interaction with infrastructure work — provisioning, configuring, deploying, monitoring, or operating infrastructure systems.
Enforces rigid checklist for writing, reviewing, or changing build scripts, CI workflows, deploy pipelines, repo setups, and evaluating new tools/dependencies.
Guides Docker multi-stage builds, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Loads when working with Dockerfiles, GitHub Actions, Terraform, or production infrastructure.