Create Milestone Skill

Use this skill when the user wants to plan and create a GitHub milestone for an upcoming release. The skill identifies what has changed since a baseline release, presents a draft for approval, and creates the milestone with all approved items.

Supports creating multiple milestones in sequence (e.g., v1.0.20, v1.0.21) by letting the user choose the baseline and which items belong to which release.

Input

The skill accepts optional parameters:

/create-milestone [VERSION] [DATE] [NOTES]

• VERSION - Target version (e.g., v1.0.20). If not provided, suggest based on latest release.
• DATE - Target release date (e.g., 2026-04-21). If not provided, ask the user.
• NOTES - Optional theme or notes (e.g., "security hardening", "federation improvements").

Output

• A GitHub milestone with description containing two tables (Issues and PRs)
• A local draft file at .scratchpad/{version}-release-notes.md with detailed release notes

Workflow

Step 1: Discover Releases and Milestones

Gather the current state of releases and milestones:

# Get recent releases (tags + dates)
gh release list --limit 10 --json tagName,publishedAt,name \
  --jq '.[] | "\(.tagName)\t\(.publishedAt)\t\(.name)"'

# Get existing milestones (to avoid duplicates and show what's already planned)
gh api repos/{owner}/{repo}/milestones --jq '.[] | "\(.number)\t\(.title)\t\(.due_on)\t\(.open_issues)\t\(.closed_issues)"'

# Git tags for reference
git tag --sort=-v:refname | grep '^v[0-9]' | head -10

Step 2: Ask the User What They Want

Present findings and ask the user to specify:

1. Which version to create a milestone for (suggest next patch bump from latest release)
2. Target date for the release
3. Baseline release to diff from -- this is critical for flexibility
4. Theme or notes for this release

Example prompt: