check-milestones

Aligns PR and issue milestones for merged Brave-core branches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/awfixers-stuff/browse --skill check-milestones-awfixers-stuff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-milestones
Source: https://github.com/awfixers-stuff/browse/tree/main/.claude/skills/check-milestones
Command: npx skills add https://github.com/awfixers-stuff/browse --skill check-milestones-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Check and fix milestones on a contributor's merged PRs and their associated GitHub issues.

Core Features & Use Cases

  • Determine PR milestones based on merged branch and Brave release channels.
  • Align issue milestones based on uplift history and merged branches.
  • Provide a summarized report and actions for milestone updates.

Quick Start

Run the check-milestones command with a GitHub username to align milestones for that author's merged PRs and linked issues.

Frequently Asked Questions about check-milestones

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

FAQPage Schema
How do I align PR and issue milestones for merged PRs in Brave-core?

Align PR and issue milestones by running the check-milestones command with a GitHub username. It identifies merged PRs and linked issues, then updates their milestones based on the Brave release schedule.

How are GitHub milestones determined for nightly, beta, and release uplift workflows?

Milestones are determined by analyzing the base branch of the merged PR, such as master, beta, or release. The tool maps these branches to the correct Brave release schedule and applies safety checks before updating.

Why are issue milestones misaligned after a PR uplift across Brave release channels?

Issue milestones become misaligned when uplift history and merged branches are not properly tracked. This tool fixes them by evaluating the uplift workflow and aligning the linked GitHub issues to the correct release milestone.

Can I automatically fix milestone issues for a specific contributor's merged pull requests?

Yes, you can fix milestone issues for a specific contributor by passing their GitHub username to the command. It processes their merged PRs and provides a summarized report of the required milestone updates.

What are the limitations of automating milestone alignment across Brave release branches?

The automation is limited to Brave-core PRs and their linked GitHub issues. It relies on the Brave release schedule to determine milestones from base branches and includes safety checks to prevent incorrect updates.

Does this tool work with GitHub issues linked to release branch pull requests?

Yes, it works with GitHub issues linked to release branch pull requests. It aligns issue milestones based on the uplift history and the specific merged branches associated with the pull requests.