ansible-verification-looplisted

# ansible-verification-loop ## Purpose Provide a structured approach for reviewing and modifying Ansible roles and collections. Ensures changes are made consistently with the target repo's own conventions, verified through a real lint/test loop, and reported clearly. It works across different repos' test setups (molecule, ansible-test, tox, pytest-ansible, etc.) by discovering what is actually there rather than assuming one project's layout. ## When to use this - Reviewing or modifying any Ansible role, collection, playbook, or task. - You need to ensure changes are consistent with existing conventions and actually verified before being reported done. ## When NOT to use this - Changes that do not involve Ansible roles, collections, playbooks, or tasks. ## Steps 1. Orient in the target role/collection before changing anything: - Read the relevant role's `defaults/main.yml`, `tasks/main.yml`, `meta/main.yml`, and any `handlers/`, `vars/`, `templates/` it touches. - For collections, also check `galaxy.yml`, `meta/runtime.yml`, and `requirements.yml` for dependencies and supported Ansible/Python versions. 2. Discover and follow the repo's own authoritative rules. Check for (roughly in priority order): `.github/copilot-instructions.md`, `.github/instructions/*.instructions.md`, `CONTRIBUTING.md`, `CLAUDE.md`, `AGENTS.md`, or a `docs/` style guide. If none exist, infer conventions from surrounding code (FQCN vs short module names, quoting style, v