release-management SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

release-management from yonatangross/orchestkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add yonatangross/orchestkit/release-management@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
yonatangross/orchestkit
Path
plugins/ork-extras/skills/release-management/SKILL.md
Versions recorded
1
Latest version
v1.0.0, committed Nov 12, 2026
Size
5,586 bytes
Repository stars
304
License
MIT

Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Release Management

Automate releases with `gh release`, semantic versioning, and changelog generation.

> **CC ≥ 2.1.118 (M122):** `claude plugin tag <version>` validates the plugin manifest hierarchy (marketplace.json, plugin.json, package.json, version.txt) before tagging. Runs `--dry-run` in CI before release-please opens its release PR; catches manifest drift early. See `src/skills/chain-patterns/references/plugin-tag.md`.

## CRITICAL: Task Management is MANDATORY (CC 2.1.16)

**BEFORE doing ANYTHING else, create tasks to track progress:**

```python
# 1. Create main task IMMEDIATELY
TaskCreate(
  subject="Release: {version}",
  description="Creating release with semantic versioning and changelog",
  activeForm="Releasing {version}"
)

# 2. Create subtasks for each release phase
TaskCreate(subject="Version & changelog", activeForm="Determining version and generating changelog")
TaskCreate(subject="Create release", activeForm="Creating GitHub release")
TaskCreate(subject="Verify & announce", activeForm="Verifying release and announcing")

# 3. Set dependencies for sequential phases
TaskUpdate(taskId="3", addBlockedBy=["2"])
TaskUpdate(taskId="4", addBlockedBy=["3"])
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3crvdu7caatc4z4q/1f215d21cfa3a48a78c893eca7bef8ff524e910b1ebea1ed669320e1add6a119.json

Then /plugin install release-management@markdownregistry-3crvdu7caatc4z4q in Claude Code. It installs v1.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add yonatangross/orchestkit/release-management@sha256:1f215d21cfa3a48a

The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_3crvdu7caatc4z4q.svg)](https://markdownregistry.com/a/art_3crvdu7caatc4z4q)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in yonatangross/orchestkit/release-management since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of release-management from somewhere else? Ask it: where did my release-management come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Nov 12, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
v1.0.0 latest2026-11-12 341c8ca 5,586 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (5586 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

yonatangross/orchestkit · 304 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_3crvdu7caatc4z4q
GET https://markdownregistry.com/api/v1/resolve?ref=yonatangross/orchestkit/release-management
GET https://markdownregistry.com/api/v1/blob/1f215d21cfa3a48a78c893eca7bef8ff524e910b1ebea1ed669320e1add6a119

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from yonatangross/orchestkit

AGENTS.md AGENTS.md file
yonatangross/orchestkit · AGENTS.md
git:20261022.980c9bf · audit A · 304 stars
CLAUDE.md CLAUDE.md file
yonatangross/orchestkit · CLAUDE.md
git:20261029.22dfd98 · audit A · 304 stars
AGENTS.md@docs/site AGENTS.md file
yonatangross/orchestkit · docs/site/AGENTS.md
git:20260823.5e31893 · audit A · 304 stars
CLAUDE.md@docs/site CLAUDE.md file
yonatangross/orchestkit · docs/site/CLAUDE.md
git:20260823.5e31893 · audit B · 304 stars
ork-assess SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-assess/SKILL.md · Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use…
git:20260819.cf231c6 · audit A · 304 stars
ork-brainstorm SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-brainstorm/SKILL.md · Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a…
git:20260819.cf231c6 · audit A · 304 stars
ork-commit SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-commit/SKILL.md · Create one Conventional Commit of the intended changes on a feature branch, with the repository's own hooks and signing…
git:20261116.0625e64 · audit A · 304 stars
ork-create-pr SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-create-pr/SKILL.md · Push the current feature branch and open a pull request with a conventional title and a summary of what changed and how…
git:20261116.0625e64 · audit A · 304 stars
ork-explore SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-explore/SKILL.md · Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a…
git:20260819.cf231c6 · audit A · 304 stars
ork-glyph SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-glyph/SKILL.md · Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories…
git:20260919.ab8d756 · audit A · 304 stars
ork-implement SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-implement/SKILL.md · Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or…
git:20260825.dc3bfe8 · audit A · 304 stars
ork-review-pr SKILL.md skill
yonatangross/orchestkit · plugins/ork-codex/skills/ork-review-pr/SKILL.md · Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use…
git:20260819.cf231c6 · audit A · 304 stars

Every file in yonatangross/orchestkit

Other files named release-management

release-management SKILL.md skill
rampstackco/claude-skills · skills/release-management/SKILL.md · Run the recurring release cycle that turns merged work into a shipped, communicated release: a stated release model, a…
git:20261116.d990d99 · audit A · 1,100 stars
release-management SKILL.md skill
yonatangross/orchestkit · plugins/ork/skills/release-management/SKILL.md · Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration…
v1.0.0 · audit A · 304 stars
release-management SKILL.md skill
andreibesleaga/gabbe · plugins/gabbe-ops/skills/release-management/SKILL.md · Manage versioning, changelogs, and release processes. Use when: Prepare a release, Draft release notes, Bump version…
git:20261014.de0823c · audit A · 23 stars
release-management SKILL.md skill
jnpiyush/agentx · .github/skills/operations/release-management/SKILL.md · Implement release management with versioning strategies, deployment strategies, rollback procedures, and release…
v2.0.0 · audit A · 19 stars
release-management SKILL.md skill
jpeetz/agent-skills · skills/git-release/release-management/SKILL.md · Use this skill when preparing a new software release — version bumping, changelog generation, git tag workflows…
git:20261026.ddc2cce · audit A · 17 stars
release-management SKILL.md skill
higoralves/orc · orc/skills/release-management/SKILL.md · Cut a semver release from conventional commits — bump, grouped changelog, annotated tag, GitHub release
git:20261020.7a1f356 · audit A · 7 stars
release-management SKILL.md skill
higoralves/orc · codex/orc/content/skills/release-management/SKILL.md · Cut a semver release from conventional commits — bump, grouped changelog, annotated tag, GitHub release
git:20261106.693b476 · audit A · 7 stars
release-management SKILL.md skill
rampstackco/claude-skills-pm · skills/release-management/SKILL.md · Run the recurring release cycle that turns merged work into a shipped, communicated release: a stated release model, a…
git:20261116.ebf3bc9 · audit A · 4 stars

Browse by kind, by grade A, or by owner.