draft-release

Draft a GitHub release with changelog notes from ./tmp/release-notes/*.md.

1.3k|142|Updated Jun 18, 2025
One-click install
npx skills add https://github.com/dyoshikawa/rulesync --skill draft-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-release
Source: https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/draft-release
Command: npx skills add https://github.com/dyoshikawa/rulesync --skill draft-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft-release workflow standardizes creating a release by validating the main branch, merging latest changes, and compiling versioned release notes for publication.

Core Features & Use Cases

  • Verifies branch state, computes new version from input or automatic release-dry-run, and prepares a release branch (e.g., release/v1.2.3).
  • Aggregates release notes from ./tmp/release-notes/*.md and constructs a draft GitHub release with a structured changelog.
  • Enforces a safe, auditable process with mandatory notes sections such as What's Changed, Contributors, and Full Changelog.

Quick Start

Follow these steps to draft a release: pull the latest changes, create a release/vX.Y.Z branch, update versioning as needed, and draft the release notes for publishing.

Frequently Asked Questions about draft-release

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

FAQPage Schema
How do I automate GitHub release notes from changelog files?

You can draft a GitHub release by creating a release/vX.Y.Z branch and updating version strings. This Skill verifies the main branch, merges latest changes, and collects changelog data to prepare structured release notes for publication.

What's the best way to create a release branch and update version strings?

Creating a release branch involves pulling latest changes and branching from main to release/vX.Y.Z. This Skill computes the new version from input or automatic release-dry-run, prepares the branch, and enforces updating version strings before publishing.

How does changelog generation work for multi-step release workflows?

Changelog generation works by aggregating individual markdown files from ./tmp/release-notes/ into a unified draft. The Skill compiles structured release notes with mandatory sections including What's Changed, Contributors, and Full Changelog for auditable publication.

Do I need to merge the main branch before drafting a new project release?

Yes, verifying the main branch status and pulling latest changes is required before drafting a release. The Skill validates the main branch state, merges latest changes, and enforces running basic checks to ensure a safe, auditable release process.

What sections are required when generating release notes for version tags?

Generating release notes requires mandatory sections including What's Changed, Contributors, and Full Changelog. The Skill enforces these structured sections to ensure the draft GitHub release is complete and auditable across version tags.

Can I use automatic versioning instead of specifying a version number manually?

Yes, automatic versioning is supported instead of manual input. The Skill computes the new version from input or through an automatic release-dry-run, then prepares the release/vX.Y.Z branch accordingly for the draft release workflow.