mcpField
M
milestones

milestones

github.com/deevusDevelopment12124 installsUpdated 22w ago
Repository

About milestones

A skill for developers managing project milestones with the tea CLI. It supports listing, viewing, creating, closing, reopening, and deleting milestones, and points to a bundled action for editing.

Key features

  1. 01List open or all milestones
  2. 02View milestone details
  3. 03Create milestones with deadlines
  4. 04Close or reopen milestones
  5. 05Delete milestones

Use cases

  1. 01Review a project's current milestones
  2. 02Create a release plan with a deadline
  3. 03Close a completed or reopen a milestone

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/deevus/tea-skills --skill milestones

After installing, type/milestonesin Claude Code to confirm it loaded.

Details

From the project README

Milestones

List

tea milestones list -o simple              # open milestones, compact output (recommended)
tea milestones list --state all -o simple   # include closed
tea milestones list --output json           # use json only when parsing is necessary
tea milestones list --fields "title,state,items_open,items_closed,duedate,description"

Show

tea milestones "v1.0"

Create

tea milestones create                                          # interactive
tea milestones create --title "v1.0" --description "First stable release"
tea milestones create --title "v1.0" --deadline "2025-06-01"   # with due date

Close / Reopen / Delete

tea milestones close "v1.0"          # or multiple: close "v0.8" "v0.9"
tea milestones reopen "v1.0"
tea milestones delete "v1.0"

Edit

The tea CLI doesn't have a milestone edit command. For the bundled action, see actions/milestones/README.md.

When resolving actions/... paths, use the actions/ directory bundled relative to this skill directory.

Pass explicit scope flags (--login, --remote, or --repo) to bundled actions when the user names a login, remote, backend, or repository. Otherwise, bundled actions use active-host-first discovery.

Tips

  • Milestones are identified by name in CLI, by ID in the API-backed milestone edit action
  • Deadlines accept date strings like 2025-06-01
  • Deleting a milestone doesn't close its issues — they just become unassigned

Comments

Markdown supported