create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
npx skills add agentic-community/mcp-gateway-registry --skill create-milestone --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: ```bash # Get recent releases (tags + dates) gh release list --limit 10 --json tagName,publishedAt,name \
- Input
- Output
- Workflow
- Step 1: Discover Releases and Milestones
- Step 2: Ask the User What They Want
- Step 3: Gather Changes Since Baseline
- Step 4: Find Corresponding Issues
- Step 5: Exclude Items Already in Other Milestones
- Step 6: Present Draft for Approval
- Step 7: Create the Milestone
- Step 8: Assign Items to the Milestone
- Step 9: Create Local Release Notes Draft
- Step 10: Present Summary and Ask About Next Milestone
- Multiple Milestone Planning
Get recent releases (tags + dates)
gh release list --limit 10 --json tagName,publishedAt,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
Get the baseline release publish timestamp for precise cutoff
List all PRs merged after the baseline release
gh pr list --state merged --search "merged:>=$RELEASE_DATE" \
Get all commits since the baseline tagWhat does the create-milestone skill do?
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
How do I install it?
Run `npx skills add agentic-community/mcp-gateway-registry --skill create-milestone --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentic-community/mcp-gateway-registry, a repository with 845 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.