← ClaudeAtlas

review-playbooklisted

Review an existing Ansible playbook and produce a structured severity report grouped by CRITICAL, WARNING, and INFO. Triggered by /review-playbook. Checks FQCN usage, idempotency patterns, no_log on secret tasks, tag coverage, deprecated syntax, become usage, and style consistency. NEVER modifies files.
3A2DEV/ansible-designer · ★ 5 · Code & Development · score 63
Install: claude install-skill 3A2DEV/ansible-designer
# review-playbook Review an Ansible playbook and produce a structured severity report. This command never modifies files. --- ## Required Inputs 1. **path + filename** — Path to the playbook to review (resolved from discovery if not provided) --- ## Behavior ### Step 1 — Discovery Run discovery per `references/discovery.md`. Use context to: - Locate the playbook if only a filename is given (search in `./`, `./playbooks/`) - Identify available roles/collections for FQCN verification ### Step 2 — Load and Analyze Read the playbook file. Analyze every task, handler reference, role include, and play-level attribute. ### Step 3 — Generate Severity Report Produce a structured report in this exact format: ``` ## Playbook Review: <filename> Reviewed: <timestamp> Plays: <count> Tasks: <count> Roles: <count> --- ### CRITICAL [List of critical issues — must fix before use in production] ### WARNING [List of warnings — should fix; may cause problems under certain conditions] ### INFO [Informational suggestions — best practices, performance hints] --- Summary: <X> critical, <Y> warnings, <Z> info ``` If there are no issues in a severity level, show: `No issues found.` --- ## Checks to Perform ### CRITICAL checks | Check | What to look for | Message format | |-------|-----------------|----------------| | Bare module names | Any task using a module without FQCN prefix | `[tasks:<line>] Task "<name>" uses bare module name '<module>' — must use FQCN '<ansible.builtin.mo