New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release Milestone

by yontrack in yontrack/yontrack

Mark every status:ready issue of a GitHub milestone as released — swap status:ready for status:released, comment "Available in <version", and close any that are still open (ready issues are normally…

MITAuto-check passedProduct & Project Management

Install Release Milestone

skills CLI
$ npx skills add yontrack/yontrack --skill release-milestone -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yontrack/yontrack release-milestone --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yontrack/yontrack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-milestone .claude/skills/release-milestone && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-milestone
GitHub stars
102
Token cost
~911 tokens
SKILL.md length
400 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Mark every status:ready issue of a GitHub milestone as released — swap status:ready for status:released, comment "Available in <version", and close any that are still open (ready issues are normally…

  • Works in 6 steps: Check the inputs → List the issues → Approval gate → …
  • Asked to release
  • SKILL.md covers Step 1 — Check the inputs, Step 2 — List the issues, Step 3 — Approval gate and Step 4 — Release each approved…, plus 3 more sections
  • Calls gh

What it does

Release Milestone is an agent skill from yontrack/yontrack. Mark every status:ready issue of a GitHub milestone as released — swap status:ready for status:released, comment "Available in <version", and close any that are still open (ready issues are normally closed already). Presents the list for approval first. Use when asked to release, close out, or mark as released the issues of a milestone.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Project management. It works with GitHub. The repository describes itself as: Continuous delivery monitoring. The licence is MIT.

When your agent uses it

  • Asked to release
  • Mark as released the issues of a milestone

Example prompts

  • “Available in <version”
  • “/release-milestone”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Check the inputs
  2. List the issues
  3. Approval gate
  4. Release each approved issue
  5. Re-query
  6. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 8b8cd43. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Milestone loads about 911 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 400 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~911

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yontrack/yontrack at commit 8b8cd43, republished under its MIT licence (© yontrack). 400 words, ~911 tokens.

Download SKILL.mdSave it as .claude/skills/release-milestone/SKILL.md (or your agent's skills folder).
name
release-milestone
description
Mark every status:ready issue of a GitHub milestone as released — swap status:ready for status:released, comment "Available in <version>", and close any that are still open (ready issues are normally closed already). Presents the list for approval first. Use when asked to release, close out, or mark as released the issues of a milestone.
user-invocable
true

/release-milestone — Release a Milestone's Ready Issues

Arguments passed: $ARGUMENTS

Two arguments, in this order:

  1. milestone — the GitHub milestone title, e.g. 5.4
  2. version — the version the issues ship in, e.g. 5.4.0 or 5.4.1

If either is missing, ask for it. Do not derive the version from the milestone: a milestone can ship in a .0 or in a patch.

All commands target yontrack/yontrack.

A status:ready issue is normally closed already: the workflow in CLAUDE.md closes an issue when it is marked ready, and the label and the milestone are what keep it findable until the release. Issues marked ready before that rule, or left open because they had no milestone yet, are still open — this skill closes those too.

Step 1 — Check the inputs

bash
gh api repos/yontrack/yontrack/milestones?state=all --paginate --jq '.[].title'

If the milestone is not in the list, stop and say so. Check that version starts with the milestone (5.4.1 for 5.4); if not, ask before going on.

Step 2 — List the issues

bash
gh issue list -R yontrack/yontrack --milestone "<milestone>" --label status:ready --state all --limit 500 \
  --json number,title,state,labels \
  --jq '.[] | "#\(.number)\t\(.title)\t\(.state)\t\([.labels[].name]|join(", "))"'

If the list is empty, say so and stop.

Step 3 — Approval gate

Show the list as a table (key, title, state, labels) with the count, and state what will happen to each issue — relabel and comment for all, close as well for the ones still open. Wait for an explicit yes. Closing issues and posting comments are outward-facing, so no approval, no action.

Show full SKILL.md (178 more words)Show less

Step 4 — Release each approved issue

Only the issues shown in Step 3:

bash
for n in <numbers>; do
  if gh issue edit $n -R yontrack/yontrack --add-label status:released --remove-label status:ready >/dev/null \
    && gh issue comment $n -R yontrack/yontrack --body "Available in <version>" >/dev/null \
    && { [ "$(gh issue view $n -R yontrack/yontrack --json state --jq .state)" = CLOSED ] \
         || gh issue close $n -R yontrack/yontrack --reason completed >/dev/null; }; then
    echo "OK #$n"; else echo "FAIL #$n"; fi
done

The label is status:released. There is no status:release, and gh rejects a label that doesn't exist. The && keeps a failed relabel from commenting or closing anyway.

On any FAIL, report the issue numbers and the error. Don't retry blindly.

Step 5 — Re-query

Run the Step 2 query again. GitHub's issue search can lag, so issues may turn up that weren't in the first list, and issues can gain the label while this runs. If any appear, don't process them silently. Show them as a new table and go back to Step 3 for them.

Step 6 — Report

Say how many issues were released, how many of them were still open and got closed, list any failures, and confirm the Step 5 query came back empty.

Rules

  • Never touch an issue the user hasn't approved, even when it matches the query.
  • Never change any label other than status:ready → status:released. ready-for-agent, initiative: …, and the type labels stay.
  • Close with the default reason (completed). Never use not planned.

© yontrack, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/release-milestone of yontrack/yontrack.

Open the folder on GitHubat commit 8b8cd43

Compare with similar skills

Release Milestone next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Milestone compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Milestone this skillyontrack/yontrack102—~911Automated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Project Managerpwrdrvr/openclaw-codex-app-server265—~1.5kAutomated safety check: PassMIT
Find Project Anomaliespenpot/penpot61k—~1.2kAutomated safety check: PassMPL-2.0
PublishQ00/ouroboros6.2k—~2.7kAutomated safety check: PassMIT
Gh Read Inspectoreclipse-rdf4j/rdf4j420—~950Automated safety check: PassBSD-3-Clause

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Project Manager

    pwrdrvr/openclaw-codex-app-server

    Manage GitHub issues and the GitHub Project board for the current repository, while keeping the local tracker in sync.

    265 GitHub stars~1.5k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Find Project Anomalies

    penpot/penpot

    Check a GitHub milestone against the Main project board, report the five anomaly types to tmp/<MILESTONE-ANOMALIES.md, and fix missing milestone assignments on request.

    61k GitHub stars~1.2k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Publish

    Q00/ouroboros

    Publish Seed specification as GitHub Issues for team-based project management

    6.2k GitHub stars~2.7k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Gh Read Inspector

    eclipse-rdf4j/rdf4j

    Retrieve GitHub issues, pull requests, and milestones with read-only, whitelisted gh commands only.

    420 GitHub stars~950 tokensUpdated today
    Product & Project ManagementAuto-check passed

  • GitHub Project Management Swarm

    ruvnet/agentic-flow

    Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.

    819 GitHub starsUsed in 6 repos~7.1k tokens
    Product & Project ManagementAuto-check passed

More from yontrack/yontrack

  • Add JSON Schema

    yontrack/yontrack

    Add a new downloadable JSON schema to the Resources page — Kotlin provider class only, auto-discovered by Spring.

    102 GitHub stars~883 tokensUpdated today
    Auto-check passed

  • Add Property Type

    yontrack/yontrack

    Add a complete Yontrack property type — Kotlin PropertyType class, GraphQL mutation provider, and all required frontend UI components (Icon, Display, Form, FormPrepare).

    102 GitHub stars~990 tokensUpdated today
    Auto-check passed

  • Add Widget

    yontrack/yontrack

    Scaffold a new Yontrack dashboard widget end-to-end — Kotlin AbstractWidget class with config data class, and two frontend components (display + form).

    102 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Fix Issue

    yontrack/yontrack

    Pick a GitHub issue, create a correctly-named branch (claude/<short-description-pipeline), implement the fix, and summarise the changes.

    102 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • New Extension

    yontrack/yontrack

    Scaffold a new Yontrack extension end-to-end — module, feature descriptor, service, GraphQL, migration, tests, and UI.

    102 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Run Initiative

    yontrack/yontrack

    Work through every ready-for-agent issue of a Yontrack initiative, optionally restricted to one milestone, one at a time, each to full completion — branch, implement, merge to the issues' base…

    102 GitHub stars~5.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release Milestone

What does Release Milestone do?

Mark every status:ready issue of a GitHub milestone as released — swap status:ready for status:released, comment "Available in <version", and close any that are still open (ready issues are normally…. Release Milestone is an agent skill from yontrack/yontrack. Mark every status:ready issue of a GitHub milestone as released — swap status:ready for status:released, comment "Available in <version", and close any that are still open (ready issues are normally closed already).

When should I use Release Milestone?

Release Milestone fits situations like: asked to release; mark as released the issues of a milestone.

How do I install Release Milestone in Claude Code?

Run `npx skills add yontrack/yontrack --skill release-milestone -a claude-code`. Or copy the skill folder (.claude/skills/release-milestone in yontrack/yontrack) into .claude/skills/release-milestone in your project. Claude Code loads it when a task matches its description.

How do I install Release Milestone in Codex?

Run `npx skills add yontrack/yontrack --skill release-milestone -a codex`. Or copy the skill folder (.claude/skills/release-milestone in yontrack/yontrack) into .agents/skills/release-milestone in your project. Codex loads it when a task matches its description.

Can I use Release Milestone in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yontrack/yontrack --skill release-milestone -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-milestone, .gemini/skills/release-milestone, .github/skills/release-milestone and .opencode/skills/release-milestone in your project.

What does Release Milestone need to run?

Going by SKILL.md and its folder, Release Milestone needs the command-line tools its instructions call (gh).

Does Release Milestone access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release Milestone safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Milestone use?

Release Milestone is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Milestone use?

About 911 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Milestone?

Skills that share tags, products or a category with Release Milestone: CCPM Project Management (automazeio/ccpm, 8.4k stars), Project Manager (pwrdrvr/openclaw-codex-app-server, 265 stars), Find Project Anomalies (penpot/penpot, 61k stars) and Publish (Q00/ouroboros, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Milestone?

yontrack (a GitHub organization) maintains it in yontrack/yontrack, which has 102 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.

Source: yontrack/yontrack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.