Maintainer skills and workflows for semi-automated Apollo community operations:
- issue review
- issue-to-PR
- PR review
- server release orchestration
- Java client release orchestration
- helm chart release orchestration
- quick-start release orchestration
These skills are designed for human-in-the-loop operation by default, with optional machine-readable handoff blocks for pipeline chaining.
Review and triage issues, propose labels, ask for missing details, and draft maintainer replies.
Default output: human-friendly summary and reply draft.
Optional: append pipeline handoff fields when output_mode=pipeline.
Convert qualified issues (bug / feature request / enhancement) into minimal draft PRs with risk gating and focused validation.
Default output: human-friendly implementation and validation summary.
Optional: append pipeline handoff fields when output_mode=pipeline.
Run maintainer-grade PR review with compatibility/regression focus, then produce a publish-ready review draft.
Default output: human-friendly review decision and findings.
Optional: append pipeline handoff fields when output_mode=pipeline.
Run Apollo Java formal release flow with checkpoint-gated automation:
- release version bump PR
- GitHub prerelease creation
- release workflow trigger (auto-publish via central-publishing-maven-plugin)
- announcement discussion creation
- post-release SNAPSHOT bump PR
- prerelease promotion to official release after publish workflow succeeds
Run Apollo server formal release flow with checkpoint-gated automation:
- release revision bump PR (
pom.xmlrevision only) - prerelease draft from
CHANGES.mdwith user-selected highlight PRs (--highlight-prs) - package workflow trigger (
release-packages.yml) and release asset verification - docker publish workflow trigger (
docker-publish.yml) - prerelease promotion to official release
- announcement discussion creation
- post-release SNAPSHOT bump PR with
CHANGES.mdarchive and milestone management
Run Apollo Helm chart release flow for apolloconfig/apollo-helm-chart with local automation and publish gates:
- detect version trigger from chart
version/appVersiondiff with docs lag fallback - run
helm lint, package both charts, move tgz todocs, and regeneratedocs/index.yaml - enforce whitelist-only git changes before commit
- create standardized release commit and generate ready-for-review PR draft
- stop at push/PR gate commands for explicit human confirmation
Run Apollo quick-start release follow-up flow with checkpoint-gated automation:
- trigger quick-start asset sync workflow (
sync-apollo-release.yml) for release version updates - wait for sync workflow completion and inspect fixed-branch PR status (
codex/quick-start-sync-<version>) - require PR merge confirmation before docker publish when sync changes exist
- trigger docker publish workflow (
docker-publish.yml) with configurable tag (default: release version) - support resume via state file and explicit checkpoint confirmations
apollo-issue-reviewapollo-issue-to-pr(only when issue is ready)apollo-pr-reviewapollo-release(for Apollo server release cycles)apollo-java-release(for formal Java SDK release cycles)apollo-helm-chart-release(for apollo-helm-chart packaging/index/PR flow)apollo-quick-start-release(for apollo-quick-start sync PR + docker publish flow)
All publish actions remain confirmation-gated by default.
Use $apollo-issue-review <issue-id>
Use $apollo-issue-to-pr <issue-id>
Use $apollo-pr-review <pr-id>
Use $apollo-java-release <release-version>
Use $apollo-release <release-version>
Use $apollo-helm-chart-release
Use $apollo-quick-start-release <release-version>
apollo-issue-review/
apollo-issue-to-pr/
apollo-pr-review/
apollo-release/
apollo-java-release/
apollo-helm-chart-release/
apollo-quick-start-release/
Each skill contains its own SKILL.md and optional references/ content.