github-milestone

Automate GitHub milestone selection, creation, and attachment for PRs and issues.

Updated Mar 31, 2026

Search Tags:#automation #workflow #github #pr #release-management #milestone #milestone-attachment

Ready to run

npx skills add https://github.com/shellicar/skills --skill github-milestone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-milestone
Source: https://github.com/shellicar/skills/tree/main/skills/github-milestone
Command: npx skills add https://github.com/shellicar/skills --skill github-milestone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Workflow for selecting, creating, and attaching the right milestone version to PRs and issues to preserve release-tracking integrity when milestones are missing or misattached.

Core Features & Use Cases

Single source of truth for milestone conventions, creation, lookup, and closing on GitHub.
Deterministic workflow: checks for open milestones, reuses existing ones when suitable, or creates the next minor or major milestone as needed.
PR integration: attaches milestones during PR creation and updates, and supports closing milestones when releases ship.
Integration-ready: coordinates with related skills like github-pr, maintenance-release, github-release, and shellicar-oss-conventions for consistent milestone handling.

Quick Start

Configure the workflow to automatically attach the appropriate milestone to new PRs and issues.

Frequently Asked Questions about github-milestone

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

FAQPage Schema

How do I automate GitHub milestone assignment for pull requests and issues?▼

You can automate GitHub milestone assignment by applying a deterministic workflow that checks for open milestones, reuses suitable existing ones, or creates the next minor or major milestone version as needed during PR creation.

What happens when there is no open milestone for a new GitHub pull request?▼

When no open milestone exists for a GitHub PR, the workflow uses a fallback mechanism to automatically create a new milestone with the next version number to preserve release tracking integrity.

Can I close GitHub milestones automatically when a release ships?▼

Yes, you can close GitHub milestones automatically when releases ship by using the provided CLI commands designed for milestone lifecycle management and closing operations.

Does this milestone attachment workflow require external dependencies?▼

No, this milestone attachment workflow operates independently with no external dependencies, running a deterministic process to handle milestone selection, creation, and attachment for GitHub repositories.

Why are my GitHub PRs missing the correct release tracking milestones?▼

Your GitHub PRs are missing milestones because they were created without automated attachment, a problem solved by applying a deterministic workflow that ensures correct release tracking during PR creation and updates.

What is the best way to manage GitHub milestone lifecycle for release tracking?▼

The best way to manage GitHub milestone lifecycle is using a single source of truth for milestone conventions that handles lookup, creation, and closing to ensure correct release tracking across repositories.