oc-release-ops

Name: oc-release-ops
Availability: InStock
Author: asfbay-bit

Automate release planning, changelog drafting, version bumping, and deployment handoff for opchain projects.

Updated May 15, 2026

Search Tags:#release management #deployment #release automation #release planning #release coordination

Ready to run

npx skills add https://github.com/asfbay-bit/opchain-skills --skill oc-release-ops

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oc-release-ops
Source: https://github.com/asfbay-bit/opchain-skills/tree/main/skills/oc-release-ops
Command: npx skills add https://github.com/asfbay-bit/opchain-skills --skill oc-release-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oc-git-ops, oc-deploy-ops, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire release process for opchain (or any opchain-managed project), closing the loop from sprints to changelogs to deployment, saving time and reducing errors.

Core Features & Use Cases

Release Planning: Propose the next semver based on changelog gaps and sprint outputs.
Changelog Drafting: Automatically generate changelog entries from sprint checkpoints and merged PRs.
Version Bumping: Atomically bump every skill version and update the homepage release-pill.
Announcement: Compose release announcements and tickets.
Deployment Handoff: Hand off to oc-git-ops and oc-deploy-ops for staging and production deployment.
Use Case: Use this Skill to streamline the release process for your opchain project, ensuring consistent, reliable releases.

Quick Start

Run the full release pipeline using the command: /oc-release ship

Frequently Asked Questions about oc-release-ops

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

FAQPage Schema

How do I automate release planning and version bumping for my project?▼

Automate release planning and version bumping by using a Skill that proposes the next semver based on changelog gaps, then atomically updates versions across your project. It coordinates deployment by handing off to git and deploy operations tools.

How do I generate a changelog from merged PRs and sprint checkpoints?▼

Generate a changelog from merged PRs by using a release automation Skill that automatically drafts changelog entries from sprint checkpoints. This closes the loop from sprints to changelogs without manual entry, ensuring consistent release documentation.

What is the best way to coordinate deployment handoff for staging and production?▼

Coordinate deployment handoff for staging and production by using a release management Skill that manages the transition to git and deploy operations. This ensures reliable deployment coordination and tracks release progress using a checkpoint protocol.

Do I need git and deploy operations tools to automate release shipping?▼

Yes, you need git and deploy operations tools to automate release shipping. The release automation Skill depends on oc-git-ops and oc-deploy-ops to execute the final staging and production deployment handoff for opchain-managed projects.

Can I compose release announcements and tickets automatically?▼

Yes, you can compose release announcements and tickets automatically. The release management Skill generates these communications as part of the automated pipeline, alongside drafting changelogs and bumping skill versions for your project.

Why use a checkpoint protocol for release management?▼

Use a checkpoint protocol for release management to track release progress and state throughout the automation pipeline. This ensures the release process maintains consistent state from sprint outputs and changelog drafting through to final deployment.