maintainer-release-ops

Automate release planning and milestone management across GitHub issues and PRs.

5.1k|806|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/vllm-project/semantic-router --skill maintainer-release-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintainer-release-ops
Source: https://github.com/vllm-project/semantic-router/tree/main/tools/agent/skills/maintainer/release-ops
Command: npx skills add https://github.com/vllm-project/semantic-router --skill maintainer-release-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers need a structured workflow to plan releases, create milestones, and track GitHub issues/PRs across teams, ensuring visibility and coordination.

Core Features & Use Cases

  • Release planning with milestone synchronization
  • State synchronization for GitHub issues and PRs with active release plans
  • Daily briefs, backlog grooming, and stale PR management
  • Governance that emphasizes generated actions and requires review before mutation

Quick Start

Run maintainer_board.py sync to refresh local state, then execute release-report when an active release plan exists to generate a proposal.

Frequently Asked Questions about maintainer-release-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub release planning and milestone management?

Automate GitHub release planning by synchronizing issues and PRs with active release cycles, generating daily briefs, and proposing backlog grooming actions for maintainer teams.

What is the best way to track stale PRs across release milestones?

Track stale PRs across release milestones by refreshing local state and running backlog grooming checks to identify inactive pull requests and propose synchronization actions.

How does review-before-mutation governance work for GitHub issues?

Review-before-mutation governance generates proposed actions for GitHub issues and milestones, requiring maintainer approval before any board state changes or mutations are executed.

Can I use this workflow for backlog grooming on large GitHub projects?

Yes, backlog grooming is supported for large GitHub projects by applying milestone health checks to synchronize boards and generate actionable proposals for maintainer review.

How do I generate a release report for an active GitHub milestone?

Generate a release report by refreshing local state with a sync command, then executing the release report action when an active release plan exists to output a review proposal.

Why does my release plan require local state refresh before action generation?

Local state refresh is required to synchronize current GitHub issue and PR data, ensuring release plans and generated actions accurately reflect the latest milestone health before mutation.