release

Publish GitHub releases from version blocks in RELEASES.md via gh.

2|Updated Jun 24, 2026

Search Tags:#automation #documentation #deployment #github #release #pdda

Ready to run

npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill release-hypercart-dev-tools

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Hypercart-Dev-Tools/pdda/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill release-hypercart-dev-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill eliminates the manual friction and potential for error when publishing software releases by synchronizing project-driven documentation with live GitHub release objects.

Core Features & Use Cases

Automated Publishing: Converts structured release blocks in RELEASES.md into official GitHub releases using the GitHub CLI.
Safety Guardrails: Provides a mandatory preview and confirmation step to ensure release notes and metadata are accurate before they go public.
Use Case: When a project reaches a milestone, use this skill to instantly generate a release body from your documented description and publish it to GitHub without leaving your terminal.

Quick Start

Ask the assistant to release version 1.0.0 to find the corresponding entry in your documentation and publish it to GitHub after your confirmation.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate GitHub releases from a markdown ledger?▼

You can automate GitHub releases from a markdown ledger by parsing version-specific blocks from a central RELEASES.md file and publishing them. This workflow validates the structured documentation and deploys it as a live GitHub release object.

Do I need the GitHub CLI to publish releases from a terminal?▼

Yes, you need the GitHub CLI (gh) to publish releases from a terminal. The CLI handles the required authentication and API interaction to ensure your release deployment is durable and public.

What is the best way to ensure release notes are accurate before publishing to GitHub?▼

The best way to ensure release notes are accurate is to use a confirmation-based workflow that provides a mandatory preview. This safety guardrail lets you validate release metadata generated from your documentation before it goes public.

Can I convert planned release documentation into live GitHub release objects?▼

Yes, you can convert planned release documentation into live GitHub release objects. By parsing version-specific blocks from your RELEASES.md ledger, the system synchronizes project-driven documentation directly with GitHub.

How does a RELEASES.md ledger work for software deployment automation?▼

A RELEASES.md ledger works for software deployment automation by acting as a central source of structured release blocks. When a project reaches a milestone, the specific version entry is extracted and validated to instantly generate a release body.

Are there limitations when transitioning planned releases to GitHub without manual friction?▼

The main limitation when automating this transition is the strict dependency on the GitHub CLI for authentication and API interaction. You must also maintain accurate, structured release blocks in your documentation to avoid publishing invalid metadata.