ai-forge

Guides the release of an Ansible collection following the upstream process (without release branches). Automatically determines the next version from changelog fragments. Outputs step-by-step instructions with commands for changelog generation, release PR, tagging, Galaxy publication, version bump, and GitHub release. Use when asked to release, publish, or tag a new collection version.

Use this skill when you need to check backport and patchback workflow blockers for Ansible collection stable branches. Detects open backport PRs and patchback failures that must be resolved before creating a release prep PR. Complements version analysis skills by focusing on process blockers. By default, checks the two most recent stable branches.

Triage bug reports, CI failures, and GitHub issues across Ansible network collections (cisco.ios, cisco.iosxr, cisco.nxos, arista.eos, ansible.netcommon, ansible.utils, etc.). Two modes: scan mode for bulk weekly triage across all repos, and direct mode for deep triage of a single issue. Network-specific: uses cross-collection cascade detection for shared dependencies (netcommon, utils) and known network CI failure patterns. Outputs structured JSON and markdown. Use when asked to triage network issues, scan network issues, weekly triage, triage CI failure, or triage collection issue. Do not use for non-network collections or general Ansible questions.

Fetch Ansible documentation from docs.ansible.com as Markdown. Use when the user asks about an Ansible topic, references a docs.ansible.com URL, or when the agent needs to look up official Ansible documentation to complete a task or verify information.

Adds SonarCloud (SonarQube Cloud) static analysis to an Ansible collection repo: sonar-project.properties, GitHub Actions scanner workflow, XML coverage for Sonar, and contributor-facing docs; includes fork/secret and assistant-safe patterns (see Security section). Use when onboarding SonarCloud, wiring CI secrets, producing coverage.xml, or mirroring ansible-collections setups like amazon.aws.

Configures CI coverage reporting for SonarCloud on Ansible collections. Use this skill when Sonar already runs but coverage is missing and you need to wire XML reports, aggregator workflows, and scanner report paths.

Determines the pull request number, status, and URL for a branch using the gh CLI. Use this skill when you need PR context for CI checks, SonarCloud analysis, or other workflows tied to an open pull request.

Determines upstream repository information and service identifiers using the gh CLI. Use this skill when you need the canonical GitHub org, repo path, or derived keys such as SonarCloud project identifiers.

Fetch, analyze, and fix SonarCloud issues with end-to-end automation. Supports both project-wide debt reduction and PR-specific quality gates. Phase A analyzes and groups issues by rule and module with priority sorting. Phase B applies fixes with validation gates, batching, and strategic approval checkpoints.

Prepare and submit a pull request for the ai-forge project. Syncs with upstream, runs quality gates (tox -e lint), commits with proper attribution, then creates the PR via gh against the upstream repo. Use when the user asks to submit, create, or open a pull request, or says "make a PR", "open PR", "create PR", "new PR".

Creates or updates changelog fragments for documenting changes in Ansible collections. Use when asked to create a changelog fragment, add a fragment, or update fragments with PR URLs. Automatically detects repository context from git.

This skill should be used when the user asks to 'commit', 'create a commit', or 'git commit'. It creates conventional commits with FQCN scopes for Ansible collection content (roles, modules, plugins).

Creates a new feature branch following project conventions. Use this skill when you need to start new work by fetching latest from origin, basing off origin/main, and configuring fork-friendly upstream tracking.

Creates a draft pull request with pre-flight checks, changelog validation, and formatted PR details. Use this skill when you are ready to open a pull request for collection changes.

Fetches the current release version from git tags, stable branches, or galaxy.yml. Use this skill when you need to determine the latest published collection version for version_added tags, changelog entries, or release planning.

Generate or update Ansible collection documentation using collection_prep. Use when module documentation needs updating, after changing module arguments or return values, before releases, or when README needs regeneration. Automatically updates module RST files and README.md with current module information.

Determines merge-base and changed files for the current branch. Use this skill when you need to identify branch-scoped changes without unrelated commits from the target branch.

Fetches GitHub Actions or GitLab CI results for a pull request or branch and analyzes failures. Use this skill when you need to diagnose CI failures, examine logs, and get suggested fixes.

Fetches Zuul CI build status and log URLs for ansible-collections pull requests. Use this skill when you need to check Zuul results, summarize failing builds, or retrieve log links for a PR.

Calculates next patch, minor, and major release versions following SemVer. Use this skill when you need to determine version_added values or answer questions about the next collection release version.

Reviews pull requests and code changes in an Ansible collection against project standards and the Ansible Collection Review Checklist. Use when asked to review a PR, patch, diff, or set of code changes. Do not use for GitHub Issues or general Q&A.

Creates or validates a project-local Python virtual environment (.venv by default) for isolated pip installs and local tooling. Typically invoked by setup-python-venv command. Use when setting up local Python dev, installing Python dependencies with pip, or before running non-Docker Python commands. Do not use when the user requests system Python, containers only, or ansible-test --docker.

Find and remediate overdue deprecation warnings in Ansible collection code. Identifies deprecated code past removal date/version and helps implement necessary changes. Use when preparing releases or cleaning up technical debt.

Runs and writes tests (sanity, unit, integration) for an Ansible collection using ansible-test. Use when asked to run, check, or write tests for a module or utility. Do not use for PR reviews or questions unrelated to testing.

Run Ansible sanity tests with smart change detection. Use when testing Ansible collections, validating module code, running pre-commit checks, or preparing releases. Supports smart mode (tests only changed files - fast), full mode (all files), and changed-only mode (custom range).

Scans Ansible collection dependencies, CI workflows, and code for security vulnerabilities. Use this skill when asked to audit security, detect hardcoded secrets, check for vulnerable packages, or validate supply chain risks before releases. Supports optional `--update` and `--fix` flags.

Analyzes Ansible collection stable branches to determine pending releases and calculate appropriate SemVer versions. Checks for unreleased commits, analyzes changelog fragments, and recommends next version. Use when asked to check which collections need releases or what version to release.

Prepares an Ansible collection release on a stable branch. Use this skill when stable-release-analyze has identified a version and you need to create a prep branch, update galaxy.yml, generate changelog entries, and run antsibull-changelog release.

Orchestrates end-to-end stable-branch collection releases. Use this skill when you want to release a collection with stable-X branches by coordinating stable-release-analyze, stable-release-prep, docs-generate, tox-lint, and sanity in sequence.

Runs configured tox linters on an Ansible collection or Python project. Use this skill when you need to validate code quality with ansible-lint, black, isort, flake8, pylint, flynt, or ruff before commits or releases.

Write or improve Ansible content (playbooks, tasks, handlers, templates, variables, inventories, argument specs) following Red Hat CoP automation good practices. Use when writing new Ansible YAML content from a description, or improving existing content against best practices. Do NOT use for Python module development (use write-module), role/collection scaffolding (use the /ansible-scaffold-role or /ansible-scaffold-collection commands), compliance auditing (use the /ansible-cop-review command), or style review (use ansible-zen).

Use this skill when implementing terminator classes and IAM permissions in the mattclay/aws-terminator repository after analysis. Creates terminator class code following Terminator/DbTerminator patterns, generates IAM permission blocks, and validates changes for PR submission. Invoke for "implement terminator", "create terminator classes", or "add terminator permissions".

Use this skill when creating an end-to-end aws-terminator PR for new AWS modules in Ansible collections. Orchestrates analysis, implementation, validation, and PR submission, linking the companion PR back to the original collection PR. Invoke for "aws terminator workflow", "create aws-terminator pr", or "terminator pr for" a collection PR.

Review and help prepare a contributor's pull request for merge. Checks that the branch is up to date, quality gates pass, PR description follows the template, and skills conform to the agentskills.io spec. Use when the user asks to review a PR, check a contributor's PR, or get a PR ready for merge.

Use this skill when writing unit or integration tests for Ansible modules with ansible-test and pytest. Covers test structure, mocking AnsibleModule, argument validation, and integration test patterns. Do NOT use for Ansible content tests (use write-content-tests for Molecule).

Use this skill when analyzing an Ansible AWS collection PR to determine what aws-terminator terminator classes and IAM permissions are needed. Fetches PR changes, checks existing terminator coverage, and generates a structured analysis report with implementation recommendations. Invoke for "analyze aws terminator", "check terminator coverage", or "what terminator classes needed".

Compare 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 this skill 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.

Write functional tests for Ansible content (roles, playbooks) using Molecule. Focuses on verifying intended outcomes — does the automation achieve its goal? — not retesting built-in modules. Use when writing new Molecule scenarios, verify playbooks, or improving existing tests. Do NOT use for Python module unit/integration tests (use write-module-tests).

Scaffold new Ansible modules or review existing ones against official best practices from docs.ansible.com. Use when writing a new module from scratch, reviewing module code for compliance, or asking how to structure an Ansible module. Do NOT use for role scaffolding, playbook review, or PR-level review.

Display the Zen of Ansible principles and review Ansible code against them. Use when the user wants to see the Zen of Ansible, get philosophical guidance on their automation approach, or review code for simplicity, readability, and clarity. Use when user says "zen of ansible", "simplify my playbook", "is this too complex", or "clean code review". Do NOT use for strict rule compliance (use ansible-cop-review instead).