check-milestones

Correct and synchronize GitHub PR and issue milestones by merge branch.

4|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/brave-experiments/brave-core-bot --skill check-milestones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-milestones
Source: https://github.com/brave-experiments/brave-core-bot/tree/main/.claude/skills/check-milestones
Command: npx skills add https://github.com/brave-experiments/brave-core-bot --skill check-milestones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that GitHub Pull Requests (PRs) and their associated issues have accurate and consistent milestones, preventing release delays and improving project tracking.

Core Features & Use Cases

  • PR Milestone Correction: Automatically sets the correct milestone for merged PRs based on the branch they were merged into (e.g., Nightly, Beta, Release).
  • Issue Milestone Synchronization: Determines the appropriate milestone for issues based on the earliest release branch a fix has been merged into, including uplifts.
  • Use Case: After a feature is merged into the main branch and then uplifted to Beta and Release, this Skill verifies and corrects the milestones on both the PRs and the linked issues to reflect their presence in the latest stable releases.

Quick Start

Run the check milestones skill for the GitHub username 'netzenbot' to review all their recent merged PRs.

Frequently Asked Questions about check-milestones

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

FAQPage Schema
How do I synchronize GitHub PR and issue milestones automatically?

To synchronize GitHub PR and issue milestones, this Skill corrects milestone assignments based on the merge branches and release schedules of merged pull requests. It manages PRs merged into main, beta, or release branches and updates linked issues.

What is the best way to manage issue milestones after uplifting a PR to a release branch?

Managing issue milestones after an uplift requires determining the earliest release branch containing the fix. This Skill updates associated issues based on uplift PRs to ensure their milestones reflect the latest stable releases.

Do I need GitHub CLI to correct pull request milestones?

Yes, you need the GitHub CLI (gh) installed to correct pull request milestones. The Skill requires this dependency to interact with repositories, verify merge branches, and fetch release information from wiki pages.

Why does an issue milestone mismatch when a feature is merged into main and uplifted to beta?

An issue milestone mismatches after an uplift because the original PR milestone does not automatically propagate to subsequent release branches. This Skill synchronizes the milestones across both PRs and linked issues to prevent release delays.

Can I update milestones for multiple merged PRs based on release schedules at once?

You can update milestones for multiple merged PRs by running this Skill for a specific GitHub username. It reviews recent merged pull requests and corrects their milestones based on the defined release schedules and merge branches.