release-manager

Coordinate monorepo release preparation with git and GitHub CLI.

15|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/LazyIsEfficient/agentic-os --skill release-manager-lazyisefficient
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/release-manager
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill release-manager-lazyisefficient

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates release preparation for a monorepo — maintaining CHANGELOG and the release assessment document, resolving merge conflicts on release branches, and communicating status, risk, and asks to the broader team.

Core Features & Use Cases

  • CHANGELOG upkeep: Maintain the user-facing changelog for each release.
  • Release assessment & risk: Create and update the release assessment document capturing risk, testing status, and rollout notes.
  • Release coordination workflow: Manage release branches, handle merge conflicts, and communicate status and asks to the team.

Quick Start

Coordinate a monorepo release by creating a release branch, updating the CHANGELOG and release assessment, opening a PR, validating checks, and tagging the release.

Frequently Asked Questions about release-manager

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

FAQPage Schema
How do I coordinate a monorepo release with multiple branches and changelogs?

Monorepo release coordination involves creating a release branch, updating the user-facing CHANGELOG, and opening a PR. You validate checks, resolve merge conflicts, and tag the release using git and GitHub CLI.

What is included in a monorepo release assessment document?

A monorepo release assessment captures risk, testing status, and rollout notes. Maintaining this document helps communicate status, risk, and asks to the broader team during the release coordination workflow.

Can I use GitHub CLI to resolve merge conflicts on a release branch?

Yes, GitHub CLI supports managing release branches and resolving merge conflicts. The workflow handles branch naming, PR processes, and semantic version tagging using git and GitHub CLI commands.

How do I maintain a user-facing changelog for a semantic version release?

Maintaining a user-facing changelog involves updating the file during release branch preparation. The workflow ensures the CHANGELOG reflects all changes before you tag the semantic version and finalize the release.

What is the best way to handle merge conflicts during monorepo release preparation?

The best way to handle merge conflicts during monorepo release preparation is through a structured release coordination workflow. This involves managing release branches, opening a PR, and validating checks before tagging the semantic version.