菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | stable-release |
| description | 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. |
| user-invocable | true |
Complete end-to-end release workflow for collections with stable-X branches.
Alina Buzachis (alinabuzachis) - Ansible Cloud Content Team
Orchestrates all release steps from analysis to PR creation for stable-branch workflows. Imports and coordinates individual skills (stable-release-analyze, stable-release-prep, docs-generate, tox-lint, sanity) in the correct order with proper error handling and user interaction.
CRITICAL: This orchestrator must minimize permission prompts by batching operations.
Key principles:
/tox-lint and /sanity in parallel using background agentsExample flow:
Message 1: Setup venv with uv/pip (antsibull-changelog, ansible-core, tox)
Message 2: Read galaxy.yml + all changelog fragments (parallel)
Message 3: Run git operations (single bash command with &&)
Message 4: Invoke /tox-lint and /sanity (parallel, run_in_background)
Message 5: Write/Edit files after analysis complete
Virtual environment setup (use uv for speed):
python3 -m venv .venv && source .venv/bin/activate && \
(command -v uv &> /dev/null && \
uv pip install antsibull-changelog ansible-core tox || \
pip install --quiet antsibull-changelog ansible-core tox)
Reads from ~/.ansible-release.conf:
export GITHUB_USERNAME="alinabuzachis"
export ANSIBLE_COLLECTIONS_PATH="~/dev/collections/ansible_collections"
export SANITY_MODE="smart"
export AUTO_CREATE_PR="prompt" # true | false | prompt
export LINT_ON_COMMIT="true"
export SANITY_ON_COMMIT="true"
# Full automated release (interactive prompts)
/stable-release
# Analyze only (no changes)
/stable-release --analyze-only
# Prepare specific version
/stable-release --collection amazon.ai --version 1.0.1 --branch stable-1
# Custom release date (future-dated or backdated)
/stable-release --collection amazon.ai --version 1.0.1 --branch stable-1 --release-date 2026-06-15
# Skip specific steps
/stable-release --skip-lint --skip-sanity
# Full automation (no prompts)
/stable-release --auto --create-pr
# Dry run (show what would happen)
/stable-release --dry-run
See references/workflow-steps.md for the full six-step orchestration sequence from analysis through pull request creation.
See references/output-example.md for a full end-to-end run.
See references/error-handling.md for recoverable and non-recoverable errors and resume capability.
| Flag | Description |
|---|---|
--analyze-only | Run analysis and stop |
--release-date YYYY-MM-DD | Custom release date (default: today) |
--skip-lint | Skip linting step |
--skip-sanity | Skip sanity testing |
--skip-docs | Skip documentation generation |
--force | Continue even if quality checks fail |
--auto | No interactive prompts (use config defaults) |
--create-pr | Automatically create PR |
--dry-run | Show what would happen without making changes |
--resume | Resume from last successful step |
This orchestrator imports:
/stable-release-analyze - Determine version needed/stable-release-prep - Create branch and changelog/docs-generate - Update documentation/tox-lint - Run linters/sanity - Run sanity testsgit commit and git push - Commit and pushgit with configured remotestox with lint and add_docs environmentsantsibull-changelog installedgh CLI (for PR creation)origin (fork), upstream (canonical)galaxy.yml with valid versiontox.ini with lint and add_docs envschangelogs/fragments/ with at least one fragment~/.ansible-release.conf with GITHUB_USERNAME0: Release workflow completed successfully1: Workflow failed at any step2: Configuration error or missing requirements130: User aborted (Ctrl+C)See references/implementation-notes.md for parallel execution, state management, user interaction, and handbook compliance guidance.