maintainer-release-ops
$
npx mdskill add vllm-project/semantic-router/maintainer-release-ops- Use when release planning needs GitHub milestone, issue, or PR management - Use when the maintainer asks for a daily board, stale PR review, backlog grooming, or milestone health check
SKILL.md
.github/skills/maintainer-release-opsView on GitHub ↗
--- name: maintainer-release-ops category: support description: Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, create milestone issues, sync GitHub issue or PR state, generate a daily review brief, or manage stale PRs and backlog routing. --- # Maintainer Release Ops ## Trigger - Use when release planning needs GitHub milestone, issue, or PR management - Use when the maintainer asks for a daily board, stale PR review, backlog grooming, or milestone health check ## Required Surfaces - `maintainer_ops` ## Stop Conditions - GitHub writes are requested but the generated action payload has not been reviewed by the maintainer - A public issue, PR, or comment body would include private infrastructure details or AI/tool attribution ## Workflow 1. Read the active release plan and maintainer policy. 2. Run `maintainer_board.py sync` to refresh local state, or `brief` to use the latest snapshot. 3. Run `release-report` when an active release plan exists, then compare plan tasks, milestone issues, and PR blockers before proposing work. 4. Review issue and PR groups by milestone, lifecycle, and stale status. 5. Generate proposed actions only; do not mutate GitHub by default. 6. Apply actions only after maintainer confirmation. ## Must Read - [docs/agent/maintainer-ops.md](../../../../../docs/agent/maintainer-ops.md) - [tools/agent/maintainer-policy.yaml](../../../maintainer-policy.yaml) - [.prowlabels.yaml](../../../../../.prowlabels.yaml) - [.github/PULL_REQUEST_TEMPLATE.md](../../../../../.github/PULL_REQUEST_TEMPLATE.md) ## Standard Commands - `python3 tools/agent/scripts/maintainer_board.py sync --milestone "<name>"` - `python3 tools/agent/scripts/maintainer_board.py brief` - `python3 tools/agent/scripts/maintainer_board.py release-report --release-plan docs/agent/plans/pl-0033-v0-3-themis-release-closure.md --write` - `python3 tools/agent/scripts/maintainer_board.py create-issues --release-plan docs/agent/plans/pl-0033-v0-3-themis-release-closure.md --dry-run` ## Gotchas - Milestone assignment is a release commitment; `milestone-candidate` is not. - Close-candidate PRs should get an explicit grace-period comment before close unless the maintainer asks for immediate closure. - The generated board is local and gitignored; do not link to local board paths from public GitHub artifacts. ## Acceptance - The local maintainer board groups issues and PRs into actionable buckets - Public GitHub actions are generated separately from read-only sync - Release issue creation follows the current release plan and default label policy
More from vllm-project/semantic-router
- config-platform-changeSynchronizes config representations across router config, Python CLI schema, and dashboard config UI. Use when adding or changing a config concept that spans those surfaces or addressing config representation debt before Kubernetes-facing translation.
- cross-stack-bugfixDiagnoses and fixes bugs that span multiple layers (runtime, CLI, UI, platform, tests) requiring coordinated changes across surfaces. Use when a bug does not map cleanly to a narrower skill, the fix touches more than one surface, or changes need cross-cutting validation.
- dashboard-platform-changeModifies dashboard frontend or backend surfaces that present, configure, or manage router behavior through the console UI. Use when changing dashboard pages or components, backend handlers, console persistence, auth or session flows, or user-visible routing metadata in the dashboard.
- fleet-sim-changeModifies the fleet simulator package, API service, release wiring, or simulator-owned docs and assets as one maintained subsystem. Use when changing src/fleet-sim, simulator release workflow, or fleet-sim-owned docs and assets under website/.
- harness-contract-changeModifies the repository's agent contract including AGENTS.md, docs index, manifests, validation scripts, and contributor-facing harness wrappers. Use when updating agent documentation, changing repo manifests, editing validation scripts, modifying CI/workflow classification, or updating contributor-facing guides like README.md, CONTRIBUTING.md, or the PR template.
- k8s-platform-changeModifies Kubernetes-facing operator, CRD, deployment-profile, or DSL translation behavior for semantic-router platform integration. Use when changing operator APIs or controllers, deployment stack manifests, profile-owned platform wiring, or router-to-Kubernetes translation layers.
- maintainer-issue-pr-managementManages GitHub issue and pull-request lifecycle including creation, updates, triage labelling, and closeout metadata using canonical templates and repository taxonomy. Use when a maintainer asks to create, update, close, or triage GitHub issues or PRs, or when issue creation requires codebase analysis for scope, labels, or acceptance criteria.
- openclaw-vsr-bridgeInstall vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR.
- plugin-end-to-endImplements end-to-end plugin changes spanning router config, post-decision processing, optional CLI/UI exposure, and E2E test coverage. Use when adding a new plugin type, changing plugin config schema or execution semantics, updating plugin chain behavior, or modifying plugin-exposed metadata across surfaces.
- router-service-platform-changeModifies router-side API, authz, memory, provider, storage, or runtime service modules outside config, decision, selection, and extproc plugin chains. Use when changing apiserver endpoints, authz or rate-limit policy code, memory or response storage flows, provider adapters, or other router service-platform modules.