milestone-modify

Update, close, or delete GitHub milestones via CLI flags.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill milestone-modify-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-modify
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/milestone-modify
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill milestone-modify-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Milestone management on GitHub is manual and error-prone. This skill updates, closes, or deletes milestones to align release timelines and maintain clean project tracking.

Core Features & Use Cases

  • Milestone updates: modify milestone titles, descriptions, and due dates.
  • Close or delete: quickly close active milestones or remove incorrect ones.
  • Auditable actions: creates traceable records of milestone changes for releases.

Quick Start

Invoke the skill to modify a milestone using /milestone-modify --number 3 --close

Frequently Asked Questions about milestone-modify

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

FAQPage Schema
How do I automate GitHub milestone updates for release tracking?

You can automate GitHub milestone updates by using a CLI tool to modify titles, descriptions, and due dates. This skill validates inputs and creates an auditable change record to maintain clean release tracking.

Can I close or delete multiple GitHub milestones at once from the command line?

Yes, you can close or delete multiple GitHub milestones at once using specific CLI flags. The skill supports targeted operations like --close and --delete across single or multiple milestones to quickly clean up project tracking.

What is the best way to ensure GitHub API constraints are met when modifying milestones?

The best way to meet GitHub API constraints when modifying milestones is to use an automation skill that validates inputs before execution. This prevents API errors during milestone updates, closures, or deletions.

Does this GitHub milestone automation work without additional dependencies?

Yes, this GitHub milestone automation works without additional dependencies. It operates independently to update, close, or delete milestones via CLI flags while adhering to GitHub API constraints.

Why should I use an automated tool instead of manual GitHub milestone management?

Manual GitHub milestone management is error-prone, whereas an automated tool ensures inputs are validated and changes are auditable. Automating updates, closures, and deletions aligns release timelines accurately without manual mistakes.

What are the limitations of modifying GitHub milestones via the CLI?

Limitations of modifying GitHub milestones via CLI include strict adherence to GitHub API constraints, meaning operations must validate input parameters like --number correctly or the API request will fail.