prepare-providers-documentation
Replace the manual commit-by-commit classification step in `breeze release-management prepare-provider-documentation` with AI-driven classification. For each provider with pending changes, analyze every PR (batched into one sub-agent per provider, not one per PR), pay special attention to potentially breaking changes by inspecting the actual diff, scope multi-provider PRs to the current provider's slice, ask the release manager when uncertain, and apply version bumps + changelog entries. Use during the regular provider release cycle as an alternative to the interactive breeze prompts.
· 实时索引
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
想先保存到本地？可下载 RuleHub 当前索引到的 GitHub 仓库压缩包。
下载 Zip| name | prepare-providers-documentation |
| description | Replace the manual commit-by-commit classification step in `breeze release-management prepare-provider-documentation` wi... |
prepare-providers-documentation
Replace the manual commit-by-commit classification step in breeze release-management prepare-provider-documentation with AI-driven classification. For each provider with pending changes, analyze every PR (batched into one sub-agent per provider, not one per PR), pay special attention to potentially breaking changes by inspecting the actual diff, scope multi-provider PRs to the current provider's slice, ask the release manager when uncertain, and apply version bumps + changelog entries. Use during the regular provider release cycle as an alternative to the interactive breeze prompts.
When to use
Use this skill when the user needs help with tasks related to prepare providers documentation.
Guidelines
- Follow repository conventions in
apache/airflow - Prefer minimal, focused changes
- Validate outputs before finishing