ansible
- 44 skills
- 0 followers
- 6 hours ago last updated
- ▌ Platform Onboarding · ansible bundleGuided developer onboarding for the ansible.platform collection. Use this skill whenever a new engineer is joining the team, someone asks "where do I start" or "how does this collection work", or when onboarding a contributor who needs to understand the architecture, codebase layout, development workflow, or how to add new resource modules. Also trigger for phrases like "onboard me", "ramp up on platform", "walk me through the codebase", "I'm new to this collection", or "help me understand the platform SDK". Even if the person just says "I need to add a new module" without context, use this skill — they likely need the onboarding path first.
- ▌ Wdio Testing · ansible bundleWrite, run, and debug WebDriverIO (WDIO) UI tests for the Ansible VS Code extension. Use when creating new WDIO specs, fixing test failures, adding webview or Lightspeed tests, or troubleshooting headless/CI execution.
- ▌ Frontend Overlay · ansibleProduct-specific frontend wrappers, API clients, and paths for ansible-ui. Use when implementing or reviewing UI in this monorepo.
- ▌ Frontend Playwright E2e · ansibleWrite, run, and debug Playwright E2E / integration / live tests. Use when writing or reviewing a *.spec.ts under playwright/, or when the user asks to run, execute, or debug E2E tests, or which env vars are required. Never print secrets. For Vitest unit/component tests, read testing_guidelines.md instead.
- ▌ Update Matrix · ansible bundleRefresh tox-ansible ENV_LIST and DOWNSTREAM_EXTRA from the community ansible-core support matrix and the Red Hat AAP lifecycle pages. Use when asked to update the matrix, sync ansible-core versions, drop EOL cores, add a new core after GA, or align with AAP lifecycle.
- ▌ Make · ansibleReference for running lint, test, generate, and image build via the Makefile. Agents MUST use make targets for quality gates — do not invoke golangci-lint, go test, or controller-gen directly unless a skill explicitly allows it for debugging. This skill is the canonical lookup for which target to use.
- ▌ Td Ade · ansibleReference 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.
- ▌ Td Tox · ansibleReference 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.
- ▌ Td Pr New · ansiblePrepare and submit a pull request. Syncs with upstream, creates a feature branch, runs quality gates (tox -e lint, tox -e py), self-reviews the diff, 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".
- ▌ Td Pr Review · ansibleGuide for handling pull request reviews, including automated (Copilot, CodeRabbit) and human reviewer feedback. Use when responding to PR comments, resolving review threads, or updating PRs after review.
- ▌ Td Rebase Pr · ansibleCheck 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.
- ▌ Td Diagnose CI · ansibleFetch CI failure logs for a PR, detect the project toolchain, and diagnose the root cause. Outputs a structured diagnosis with the failure category, affected files, and suggested fix strategy. Use when a PR has failing CI and you need to understand why.
- ▌ Td Fix Bot Prs · ansibleOrchestrator that finds broken renovate/dependabot PRs across Ansible devtools repos, diagnoses failures, applies safe fixes, verifies locally, pushes, and monitors CI. Composes scan-bot-prs, rebase-pr, diagnose-ci, and verify-local into a single automated workflow.
- ▌ Td Ansible Lint · ansibleReference 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.
- ▌ Td Scan Bot Prs · ansibleScan 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.
- ▌ Td Verify Local · ansibleDetect the project toolchain and run fast, deterministic checks locally before pushing. Runs lint and package checks only — lets CI handle full tests. Never push without this skill passing.
- ▌ Td Release Order · ansibleCheck release status of all devtools projects, determine which need releasing, and output the correct release order based on runtime dependencies. Shows PyPI versions, unreleased commits, and pending bot PRs between stages. Use when planning monthly devtools releases.
- ▌ Td Skill Refresh · ansibleInstall or update the shared Team DevTools agent skills globally. Sets up periodic auto-refresh so skills stay current without manual intervention. Use when the user says "refresh skills", "update skills", "install td skills", "skill refresh", or "set up auto-update".
- ▌ Td Ansible Creator · ansibleReference 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.
- ▌ Td Supply Chain Audit · ansible bundlePerform a supply chain vulnerability analysis across ADT ecosystem repos. Verifies commit signing, PR traceability, CI integrity, and dependency provenance within a time frame. Generates a standalone HTML dashboard report and PDF.
- ▌ Td Architecture Diagram · ansible bundleGenerate professional C4 architecture diagrams of the Ansible Dev Tools ecosystem by cloning and introspecting actual repos. Produces PNG output for the AAP Miro board. Use when the user says 'architecture diagram', 'C4 diagram', 'generate diagram', 'update architecture', or references AAP-77196.
- ▌ Td Pr Contributor Review · ansibleUse when reviewing and preparing a contributor's pull request (upstream or fork). Use when the user asks to review a PR, get a contributor PR ready, update a contributor's branch, ensure a PR meets project standards before merge, or leave an agent-executable follow-up comment for another session.
- ▌ Tox · ansibleReference for running lint, test, build, and pod 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.
- ▌ Dr New · ansible bundleCreate a Decision Request. Use when you have a question that needs deciding, "we need to make a decision about X", "capture this as a DR", "log this blocking question", or after discussing something that needs formal resolution. Do NOT use for resolving DRs (use dr-review instead) or documenting decided architecture (use adr-new instead).
- ▌ Pr New · ansiblePrepare and submit a pull request for the APME project. Syncs with upstream, creates a feature branch, runs quality gates (tox -e lint, tox -e unit), updates documentation and ADRs 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".
- ▌ Adr New · ansible bundleCreate an Architecture Decision Record. Use when documenting an architecture decision, "record this choice", "we decided to use X", or after resolving an architectural DR. Do NOT use for capturing questions (use dr-new instead) or reviewing existing ADRs (use sdlc-status instead).
- ▌ Lean CI · ansibleGuide for writing and modifying GitHub Actions workflows in this repository. Use when creating CI/CD pipelines, adding workflow jobs, modifying build steps, or debugging CI failures. Enforces the project's lean CI philosophy.
- ▌ Req New · ansible bundleCreate a Requirement spec. Use when adding a new feature, "I want to spec out X", "new feature request", "create REQ for this", or when ready to formalize a feature idea. Do NOT use for creating tasks (use task-new instead) or bulk importing from PRD (use prd-import instead).
- ▌ Task New · ansible bundleCreate implementation tasks for a requirement. Use when breaking down a REQ, "add task to REQ-001", "create work items", or after approving a requirement. Do NOT use for creating requirements (use req-new instead) or reviewing task status (use sdlc-status instead).
- ▌ Workflow · ansible bundleGet workflow guidance for spec-driven development. Use when unsure what to do next, "help me get started", "what should I work on", "I'm stuck", or starting a new session. Do NOT use for directly creating artifacts (this skill guides you to the right skill for that).
- ▌ Dr Review · ansible bundleResolve open Decision Requests. Use when deciding DRs, resolving blockers, "what should we do about DR-X", "decide the blocking question", or when `/sdlc-status` shows blocking DRs. Do NOT use for creating new DRs (use dr-new instead) or just viewing status (use sdlc-status instead).
- ▌ Phase New · ansibleCreate a delivery phase for grouping requirements. Use when defining roadmap phases, "add a phase", "create Phase 2", or organizing requirements into delivery milestones. Do NOT use for importing phases from a PRD (use prd-import instead) or creating requirements (use req-new instead).
- ▌ Prd Import · ansibleImport a Product Requirements Document and create SDLC artifacts. Use when you have a PRD to break down, "import this PRD", "create specs from requirements doc", or starting a new project from a PRD. Do NOT use for updating existing artifacts or creating individual requirements (use req-new instead).
- ▌ Rfe Capture · ansibleCapture an external RFE (Jira, customer request, feature idea) using a research-first approach. Use when: "capture this Jira", "customer RFE", "feature request from X", "AAPRFE-123 should be tracked". This skill researches existing capabilities BEFORE creating specs to avoid duplicating what already exists. Do NOT use for internal feature ideas already discussed (use req-new instead).
- ▌ Sdlc Status · ansible bundleShow project status, progress, and blockers. Use when asking "what's the status?", "where are we?", "what's blocking?", "show me progress", or starting a work session. Do NOT use for creating or modifying artifacts (use req-new, dr-new, etc. instead).
- ▌ Branch Align · ansibleAlign branch name with artifact ID when they mismatch. Use when: renumbering a REQ/DR/ADR after branch creation, "branch name is wrong", "rename branch to match", or when PR review flags branch/artifact mismatch. Handles the git branch rename and remote update.
- ▌ Docs QA Audit · ansible bundleAudit documentation coverage against common user questions. Generates a Q&A matrix, searches docs/code for answers, flags gaps, and creates DRs for missing content. Use when asked to "audit docs", "check documentation coverage", "what questions can users answer", or before releases/demos.
- ▌ Security Scan · ansible bundleScan project dependencies and CI workflows for known vulnerable packages. Use when checking for security issues, "scan for vulnerabilities", "check for compromised packages", or after a security advisory is published. Extensible via references/vulnerable-packages.md.
- ▌ Check Skill Spec · ansibleCompare the agentskills.io specification against this project's extended frontmatter allowlist to determine whether the custom validation hook (scripts/check_skill_frontmatter.py) is still needed. Use when checking if the upstream spec has adopted the extended fields, when planning to remove the custom hook, or when a new spec release is announced.
- ▌ Pr Address Feedback · ansibleGuide for handling pull request reviews, including automated (Copilot, CodeRabbit) and human reviewer feedback. Use when responding to PR comments, resolving review threads, or updating PRs after review.
- ▌ Pr Contributor Review · ansibleReview and help prepare a contributor's pull request (upstream or fork). Use when the user asks to review a PR, get a contributor PR ready, update a contributor's branch, or ensure a PR meets project standards before merge. Prefer reviewing hosted CI results over reproducing the full test suite locally. Follow this skill so contributor PRs are reviewed consistently and avoid rework (failed CI, outdated base, weak description).
- ▌ Creating Backports · ansibleCreate backports of a GitHub pull request that has merged into the devel branch in the upstream repository
- ▌
- ▌ Context · ansibleLoad Ansible project development guidelines, testing conventions, PR review processes, and code structure reference into context