release-milestones

Reconcile shipped pull requests and maintain Chromium-derived release milestone dates.

5.6k|645|Updated Feb 22, 2016
One-click install
npx skills add https://github.com/mono/SkiaSharp --skill release-milestones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-milestones
Source: https://github.com/mono/SkiaSharp/tree/main/.agents/skills/release-milestones
Command: npx skills add https://github.com/mono/SkiaSharp --skill release-milestones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of SkiaSharp need to keep GitHub release milestones accurate: shipped pull requests and linked issues must map to the correct release, upcoming milestone dates must follow the Chromium schedule, and shipped milestones must be closed with open work rolled forward. Doing this manually is error-prone and tedious.

Core Features & Use Cases

  • Assignment Reconciliation: Maps merged pull requests and linked issues to the release where they shipped via reconcile-release-assignments.ps1.
  • Milestone Maintenance: Updates upcoming Chromium-derived milestone dates, rolls open work to the next unshipped milestone, and closes shipped milestones via update-release-milestones.ps1.
  • Safe Read-Only Preview: Runs both operations without -Push first so maintainers can review changes before applying them remotely.
  • Use Case: After shipping SkiaSharp 4.153.0, a maintainer runs the read-only reconciliation, reviews the proposed assignment and milestone changes, then re-runs with -Push to apply them.

Quick Start

Ask the assistant to run a read-only release milestone reconciliation for the shipped SkiaSharp version and review the output before pushing any changes.

Frequently Asked Questions about release-milestones

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

FAQPage Schema
How do I reconcile shipped pull requests to a release milestone?

Run reconcile-release-assignments.ps1 with the shipped version, for example -Version 4.153.0, first without -Push for a read-only review. After confirming the output, re-run with -Push to apply the assignment changes remotely.

How do I update GitHub milestone dates based on the Chromium schedule?

Run update-release-milestones.ps1 to refresh upcoming Chromium-derived dates, roll open work to the next unshipped milestone, and close shipped milestones. Use -Push only after reviewing the read-only output.

Does the milestone script create releases, tags, or branches?

No. The scripts never create release branches, tags, packages, or GitHub Releases. They only reconcile issue and pull request assignments and maintain milestone dates and closure state.

Why did the milestone reconciliation not apply my changes?

Changes are only applied when the -Push flag is passed; without it the scripts run read-only. Warnings in the output also block remote reconciliation or milestone closure until resolved.

Can I preview milestone changes before pushing them to GitHub?

Yes. Both scripts support a read-only mode by omitting -Push, which is the recommended first step. Always present the read-only output and request confirmation before running with -Push.