GitHub Milestone Analyzer

VerifiedSafe

Analyze GitHub milestone progress, list associated issues, and suggest next steps for a specific version release.

Sby Skills Guide Bot
DevelopmentIntermediate
406/2/2026
Claude Code
#github#milestones#release-management#project-tracking

Recommended for

Our review

Analyzes GitHub milestone progress by listing open/closed issues and suggesting next steps.

Strengths

  • Automates milestone status checks via GitHub API
  • Auto-detects mode (list or detail) based on user input
  • Normalizes version numbers to avoid format errors

Limitations

  • Requires `gh` CLI installed and configured with a valid token
  • Constrained to the `zeroae/zae-limiter` repository (specific fork)
  • Does not support advanced filters (by label or assignee)
When to use it

When you need to quickly assess release progress or list open milestones.

When not to use it

If you lack repository access or require complex reports (burn-down, statistics).

Security analysis

Safe
Quality score85/100

The skill uses only read-only GitHub CLI commands (gh api, gh issue list, gh issue view) to fetch public milestone data. No external URLs, no destructive operations, no token exfiltration, and no execution of arbitrary code. Safe.

No concerns found

Examples

Check milestone status
Check the status of milestone v0.4.0
List all milestones
/milestone list

description: When users mention a milestone version (e.g., "0.4.0", "v0.4.0") or ask about release status, invoke this skill to analyze GitHub milestone progress, issues, and suggest next steps. argument-hint: [version] | list allowed-tools: Bash(gh api:), Bash(gh issue list:), Bash(gh issue view:*) context: fork model: haiku

Milestone Skill

Analyze and summarize GitHub milestone status.

Modes

| Mode | Trigger | Purpose | |------|---------|---------| | Status | /milestone 1.0.0, /milestone v0.7.0 | Analyze specific milestone | | List | /milestone list, /milestone (no args) | Show all open milestones |

Mode Detection

  1. If version number provided (e.g., 1.0.0, v0.7.0, 0.5) → Status mode
  2. If list keywordList mode
  3. If no argumentsList mode

Status Mode

Extract the version from the user input. Normalize it (add "v" prefix if missing, e.g., 1.0.0v1.0.0).

Run these commands (replace VERSION with the normalized version):

Step 1: Get milestone details:

gh api repos/zeroae/zae-limiter/milestones --jq '.[] | select(.title == "VERSION") | {title, description, state, open_issues, closed_issues}'

Step 2: List all issues:

gh issue list --milestone "VERSION" --state all --json number,title,state,labels --jq '.[] | "\(.state)\t#\(.number)\t\(.title)"'

Step 3: If any issue title starts with "🎯", get its body:

gh issue view <number> --json title,body

See status.md for output format.

List Mode

Run this command:

gh api repos/zeroae/zae-limiter/milestones --jq '.[] | "- \(.title): \(.description)"'

Output the results.

Related skills