releasing-coplan

Publish the coplan-engine gem to RubyGems.org with version bumps, commits, and GitHub releases.

23|9|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/block/coplan --skill releasing-coplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasing-coplan
Source: https://github.com/block/coplan/tree/main/.agents/skills/releasing-coplan
Command: npx skills add https://github.com/block/coplan --skill releasing-coplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines and standardizes releasing the coplan-engine gem to RubyGems.org, reducing manual steps and errors during version bumps, commits, tagging, and publishing.

Core Features & Use Cases

  • Version bump, commit, and tag workflow for a new gem release.
  • Build and publish the gem to RubyGems.org, including handling MFA prompts.
  • Create a GitHub release with generated notes and provenance.

Quick Start

Run the release workflow to publish a new coplan-engine version to RubyGems.org.

Frequently Asked Questions about releasing-coplan

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

FAQPage Schema
How do I publish a Ruby gem to RubyGems with git tagging and a GitHub release?

Ruby gem version bumping involves updating the version constant in the version.rb file, committing the change to git, and applying a semantic tag to mark the release point before building and pushing the gem package to RubyGems.org.

How does RubyGems MFA work during gem push?

RubyGems MFA during gem push requires manual confirmation through an OTP prompt. The release process implements interactive steps to handle these MFA prompts securely when pushing the built gem package to RubyGems.org.

Do I need to manually edit version.rb before building a Ruby gem release?

You do not need to manually edit version.rb before building a Ruby gem release. The workflow automatically applies the version bump directly to the version.rb file, then commits and tags the changes for you.

What is the best way to automate gem publishing and git tagging for a Ruby project?

The best way to automate gem publishing and git tagging for a Ruby project is using a standardized workflow that bumps versions, commits, tags, builds the gem, pushes to RubyGems, and creates a GitHub release with generated notes.

Why does my gem release workflow fail during RubyGems publishing?

A gem release workflow might fail during RubyGems publishing if MFA prompts are not handled correctly or if manual confirmation steps are skipped. The process requires interactive OTP input to successfully push the gem to RubyGems.org.