// Reference for running lint, test, build, and doc commands via tox. Agents MUST use tox for all quality gates — never invoke pytest, ruff, mypy, prek, or shell scripts directly. This skill is the canonical lookup table for which tox environment to use.
| name | tox |
| description | Reference for running lint, test, build, and doc commands via tox. Agents MUST use tox for all quality gates — never invoke pytest, ruff, mypy, prek, or shell scripts directly. This skill is the canonical lookup table for which tox environment to use. |
| argument-hint | [environment-name] |
| user-invocable | true |
| metadata | {"author":"Ansible DevTools Team","version":"1.0.0"} |
/tox # Show full environment reference
/tox lint # How to run lint
/tox py # How to run tests
/tox docs # How to build docs
/tox <env> # Lookup any tox environment
tox is the only way to run lint, test, build, and doc commands in this
project. Do not invoke pytest, ruff, mypy, prek, or shell scripts
directly. Every task maps to a tox -e <env> command.
pytest directly. Use tox -e py.ruff, mypy, or prek directly. Use tox -e lint.--. Example: tox -e py -- -k test_example.uvx --with tox-uv tox -e <env> instead of installing tox.| Environment | What it runs | When to use |
|---|---|---|
tox -e lint | prek run --all-files (ruff, mypy, biome, tombi, codespell, ansible-lint) | Before every commit. Verification step for all tasks. |
| Environment | What it runs | When to use |
|---|---|---|
tox -e py | pytest with coverage (threshold varies per repo) | After any code change. |
tox -e py -- -k <pattern> | Single test or test pattern | Debugging a specific test. |
tox -e py -- --no-cov | Tests without coverage overhead | Quick iteration. |
tox -e devel | Tests with newest deps (no lock, prereleases allowed) | Verifying forward compatibility. |
| Environment | What it runs | When to use |
|---|---|---|
tox -e docs | mkdocs build --strict | After doc changes. |
| Environment | What it runs | When to use |
|---|---|---|
tox -e pkg | python -m build + twine check --strict | Before release. Verify package metadata. |
| Environment | What it runs | When to use |
|---|---|---|
tox -e deps | prek run deps + prek autoupdate + tox -e lint | Bumping all dependencies. |
Running tox with no -e flag executes the default environment list defined
in the repo's pyproject.toml or tox.ini. This is the full quality gate.
Note: Not all environments listed above are available in every repo. Run
tox l to discover the environments available in the current repository.
tox -e lint # check style + types
tox -e py # run tests
tox -e docs # build and verify docs
tox -e py -- -k test_example
tox -e py -- test/test_example.py::test_specific_function
tox -e lint
tox -e py
tox l
uv tool install tox --with tox-uv
Tox configuration typically lives in pyproject.toml under [tool.tox] or in
a standalone tox.ini. Environment definitions, extras, pass-through env vars,
and commands are all there. Do not scatter test/lint invocations across
Makefiles, scripts, or workflow YAML.
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".