← ClaudeAtlas

new-conflisted

Generate an annotated ansible.cfg for a specific environment. Triggered by /new-conf. Asks for target environment (dev, CI, or AWX) and generates a fully annotated ansible.cfg covering all official sections including defaults, privilege escalation, SSH connection, vault config, callback plugins, and fact caching. Shows summary before writing.
3A2DEV/ansible-designer · ★ 5 · DevOps & Infrastructure · score 63
Install: claude install-skill 3A2DEV/ansible-designer
# new-conf Generate an annotated ansible.cfg for a specific environment. --- ## Required Inputs 1. **target_path** — Where to write the ansible.cfg (default: `./ansible.cfg`; warn if one already exists) 2. **environment** — Target environment: - `dev` — development workstation, local VMs - `ci` — CI/CD pipeline (GitHub Actions, GitLab CI, Jenkins) - `awx` — AWX / Ansible Automation Platform --- ## Behavior ### Step 1 — Discovery Run discovery per `references/discovery.md`. Check if an ansible.cfg already exists at the target path. If it does: ``` An ansible.cfg already exists at ./ansible.cfg. Overwriting it will replace all current settings. Use /ansible-designer:update-conf to make targeted changes instead. Proceed with overwrite? (yes/no) ``` ### Step 2 — Parameter Collection Ask for environment if not provided. Show options: ``` Which environment is this ansible.cfg for? 1. dev — Development (local VMs, permissive settings, verbose output) 2. ci — CI/CD pipeline (strict, no interactive prompts, minimal output) 3. awx — AWX / Automation Controller (callback plugins, fact caching) Enter 1, 2, or 3: ``` ### Step 3 — Pre-Write Confirmation Show summary: ``` Will create: ./ansible.cfg (dev profile) Sections: [defaults] — inventory=./inventory, forks=10, yaml callback, profile_tasks [diff] — always=True, context=5 [privilege_escalation] — become=True, sudo [ssh_connection] — pipelining=True, ControlMaster=auto [persi