菜单
Configure Dependabot to keep Ansible Python tooling (ansible, ansible-lint) up to date via the uv ecosystem. Covers what Dependabot can and cannot automate for Ansible projects.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Install and configure Prettier for JavaScript/TypeScript projects. Use when setting up a dev environment, fixing formatting issues, or asked to "install prettier", "configure prettier", or "set up code formatting".
Core principles and golden rules for writing production-quality Ansible automation, covering FQCN requirements, module selection guidance, and execution patterns using uv run.
Production-grade Ansible role structure patterns for directory layout, variable organization (defaults vs vars), handlers, and task organization, derived from analysis of 7 geerlingguy production roles.
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
Configure or update Go projects with opinionated best practices using Go modules, golangci-lint, and built-in testing. Use when a repo should contain a Go project with modern tooling, idiomatic Go code, and 80% test coverage requirements.
Configure or update Python projects using uv, ruff, and pytest with opinionated best practices. Use when a repo should contain a Python project with modern tooling, PEP standards, and 80% test coverage requirements.
| name | ansible-dependabot |
| description | Configure Dependabot to keep Ansible Python tooling (ansible, ansible-lint) up to date via the uv ecosystem. Covers what Dependabot can and cannot automate for Ansible projects. |
| when_to_use | Use when setting up Dependabot for an Ansible project, adding automated dependency updates for Ansible tooling, or asked to "set up Dependabot for Ansible". |
Dependabot covers the Python tooling side of Ansible (the ansible, ansible-lint,
and related packages managed by uv). It does not support Ansible Galaxy collections
(requirements.yml) — see the note at the bottom.
| Dependency type | Supported | Ecosystem |
|---|---|---|
ansible, ansible-lint, etc. (pyproject.toml) | ✅ Yes | uv |
| GitHub Actions workflows | ✅ Yes | github-actions |
Ansible Galaxy collections (requirements.yml) | ❌ No | — |
Locate the pyproject.toml that manages Ansible tooling. It is typically at the
repo root or in an ansible/ subdirectory. Check:
find . -name "pyproject.toml" | grep -v ".venv"
Check if .github/dependabot.yml already exists.
Add a uv entry for each directory containing a pyproject.toml. For example,
if pyproject.toml is in the repo root:
version: 2
updates:
- package-ecosystem: 'github-actions'
directory: '/'
schedule:
interval: 'weekly'
- package-ecosystem: 'uv'
directory: '/'
schedule:
interval: 'weekly'
If pyproject.toml lives in an ansible/ subdirectory instead:
version: 2
updates:
- package-ecosystem: 'github-actions'
directory: '/'
schedule:
interval: 'weekly'
- package-ecosystem: 'uv'
directory: '/ansible'
schedule:
interval: 'weekly'
Commit and push .github/dependabot.yml. Dependabot will open PRs when new
versions of ansible, ansible-lint, or other uv-managed packages are released.
Ansible Galaxy collection versions pinned in requirements.yml are not a supported
Dependabot ecosystem. Those updates must be handled manually or via Renovate Bot.