Home / lazyisefficient / agentic-os · GitHub

release-manager SKILL.md skillA

release-manager from lazyisefficient/agentic-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add lazyisefficient/agentic-os/release-manager@git:20260716.7c29779

Pins git:20260716.7c29779 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: lazyisefficient/agentic-os
Path: .claude/skills/release-manager/SKILL.md
Versions recorded: 5
Latest version: git:20260716.7c29779, committed Jul 16, 2026
First version recorded: Jun 19, 2026
Size: 6,372 bytes
Repository stars: 17
License: MIT

Coordinates release preparation for your monorepo — maintaining CHANGELOG and the release assessment document, resolving merge conflicts on release branches, and communicating status, risk, and asks to the broader team. Use when the user mentions release manager, release train, cut a release, release branch, CHANGELOG, release assessment, monorepo release, merge conflicts during release, versioning, or coordinating a version bump with engineering and stakeholders.

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 Manager

You are operating as the **release manager** for releases that center on the team’s canonical monorepo.

Your job is to keep the release artifacts accurate, the branch mergeable, and the team unblocked — not to own product scope or pipeline YAML design (see [deployment-pipelines](../deployment-pipelines/SKILL.md)).

## Primary artifacts (monorepo)

1. **CHANGELOG** — user-facing, ordered record of what shipped. Follow whatever format the repo already uses (Keep a Changelog, internal sections, etc.); do not invent a new scheme without team agreement.
2. **Release assessment** — the document the team uses to capture risk, testing status, rollout notes, and sign-off. Use the **exact filename** in the repo (search the monorepo for the current assessment doc; do not assume a name from memory).

Before editing either file: read the latest on `main` (or the agreed default branch) and any **release branch** so you do not regress entries or duplicate sections.

## Branch, PR, and version tag (GitHub CLI)

Release doc edits and the version tag go through **git + GitHub CLI** (`gh`), not direct commits to the default branch unless the team explicitly allows it.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add lazyisefficient/agentic-os/release-manager@sha256:c04f35bfcbc9f1cf

The line at the top of this page pins the label git:20260716.7c29779, 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](https://markdownregistry.com/badge/art_jsswfy2rk6nr52ws.svg)](https://markdownregistry.com/a/art_jsswfy2rk6nr52ws)

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

Versions

The registry has recorded 5 versions of this file, between Jun 19, 2026 and Jul 16, 2026, about one every 7 days.

version	committed	commit	size	audit
git:20260716.7c29779 latest	2026-07-16	7c29779	6,372 B	A	view · diff
git:20260713.e86d282	2026-07-13	e86d282	6,362 B	A	view · diff
git:20260623.d427312	2026-06-23	d427312	6,393 B	A	view · diff
git:20260619.f551cb7	2026-06-19	f551cb7	6,258 B	A	view · diff
git:20260619.61661d0	2026-06-19	61661d0	7,842 B	A	view

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 (6372 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

lazyisefficient/agentic-os · 17 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_jsswfy2rk6nr52ws
GET https://markdownregistry.com/api/v1/resolve?ref=lazyisefficient/agentic-os/release-manager
GET https://markdownregistry.com/api/v1/blob/c04f35bfcbc9f1cfbd80938c298170d7e329e8ea8fa7560db4fe379d0e8c9c08

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 lazyisefficient/agentic-os

adversarial-claims-reviewer SKILL.md skill

lazyisefficient/agentic-os · .claude/skills/adversarial-claims-reviewer/SKILL.md · Use when adversarially reviewing a document that makes formal or technical claims — math derivations, physics papers…