// Reference for ansible-dev-environment (ade), a pip-like installer for Ansible collections with isolated virtual environments. Use ade to set up development environments that install both Python and collection dependencies, with proper symlinks for editable collection development.
Reference for scaffolding Ansible content with ansible-creator. Use ansible-creator to initialize new collections, playbook projects, and execution environments, or to add plugins and resources to existing projects. This skill is the canonical lookup table for which subcommand and flags to use.
Reference for linting Ansible playbooks, roles, and collections with ansible-lint. Agents should prefer tox -e lint when available, but this skill provides the canonical reference for ansible-lint options, profiles, rule suppression, and configuration when direct invocation is needed or when understanding lint output.
Check out a PR branch, rebase it onto the base branch, push, and wait for CI to complete. Reports whether the rebase alone fixed CI or if further action is needed. Use when a PR is stale and may just need a rebase to pass CI.
Scan Ansible devtools repos for open PRs from renovate and dependabot, check their CI status, and produce a prioritized list of failing PRs. Use to get a quick overview of which bot PRs need attention.
Prepare and submit a pull request. Syncs with upstream, creates a feature branch, runs quality gates (tox -e lint, tox -e py), updates documentation as needed, commits with conventional commits, then creates the PR via gh. Use when the user asks to submit, create, or open a pull request, or says "submit PR", "open PR", "create PR", "new PR".
Use when handling pull request reviews, including automated (Copilot) and human reviewer feedback. Use when responding to PR comments, resolving review threads, or updating PRs after review.
| name | ade |
| description | Reference for ansible-dev-environment (ade), a pip-like installer for Ansible collections with isolated virtual environments. Use ade to set up development environments that install both Python and collection dependencies, with proper symlinks for editable collection development. |
| argument-hint | [subcommand] |
| user-invocable | true |
| metadata | {"author":"Ansible DevTools Team","version":"1.0.0"} |
/ade # Show full subcommand reference
/ade install # How to set up a dev environment
/ade uninstall # How to tear down
ade (ansible-dev-environment) is a pip-like installer for Ansible collections
that creates isolated virtual environments. It reads galaxy.yml to determine
collection metadata and installs both Python and Ansible collection
dependencies.
--venv <path> to isolate the environment. Never install into the system Python.galaxy.yml must be present. ade reads it for collection metadata — the command must be run from a directory containing galaxy.yml or the path must point to one.-e (editable install) for development. This symlinks the collection into site-packages so changes are reflected immediately.source <venv>/bin/activate after install.| Command | What it does | Example |
|---|---|---|
ade install -e .[test] --venv .venv | Editable install with test extras | Set up a collection for development and testing |
ade install -e .[dev,test] --venv .venv | Editable install with multiple extras | Include both dev and test dependencies |
ade install -e . --venv .venv | Editable install without extras | Minimal development setup |
ade uninstall <namespace>.<name> --venv .venv | Remove collection from venv | ade uninstall ansible.scm --venv .venv |
| Behavior | Detail |
|---|---|
Uses uv when available | Falls back to pip if uv is not installed. Set SKIP_UV=1 to force pip. |
Editable installs (-e) | Symlinks the collection into site-packages for live development |
| Collection dependencies | Reads galaxy.yml dependencies and installs from Galaxy |
| Python dependencies | Processes requirements.txt and test-requirements.txt |
| Requires ansible-core | Must be pre-installed in the target venv or system |
git clone <collection_repo>
cd <collection_repo>
ade install -e .[test] --venv .venv
source .venv/bin/activate
rm -rf .venv
ade install -e .[test] --venv .venv
source .venv/bin/activate
ade install -e .[test] --venv .venv
source .venv/bin/activate
tox -e py # see the /tox skill
Ensure uv is installed and available on PATH. ade will use it
automatically. To force pip instead, set SKIP_UV=1:
SKIP_UV=1 ade install -e .[test] --venv .venv
pip3 install ansible-dev-tools # recommended: includes all devtools
pip3 install ansible-dev-environment # standalone
ade reads galaxy.yml at the collection root for metadata, dependencies,
and extras. There is no separate ade configuration file. Ensure galaxy.yml
is present and valid before running ade commands.