release

Generate a changelog, bump the version, and open a release PR.

3|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/YanCheng-go/danskprep --skill release-yancheng-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/YanCheng-go/danskprep/tree/main/.claude/skills/release
Command: npx skills add https://github.com/YanCheng-go/danskprep --skill release-yancheng-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces manual release chores by automatically collecting changes since the last tag, updating version metadata, generating a changelog, and opening a release PR.

Core Features & Use Cases

  • Generate a changelog entry from commits since the last release tag.
  • Bump the project version and synchronize changelog, constants, and package metadata.
  • Create a focused release PR to streamline deployment and review.

Quick Start

Run the release workflow to create a new versioned release for the current main branch.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a versioned release with a changelog and a pull request?

Automating a versioned release involves collecting commits since the last tag, updating version metadata, generating a changelog, and opening a release PR to streamline deployment and review.

What is the best way to generate a changelog from merged PRs for a GitHub project?

Generating a changelog from merged PRs requires detecting the last release tag, collecting subsequent changes, and synchronizing the updated entries into the project's changelog file.

How do I bump a project version and update package metadata automatically?

To bump a project version automatically, the workflow collects changes since the last release, updates the project version, and synchronizes constants and package metadata accordingly.

Do I need a clean working tree to create an automated release PR?

Yes, creating an automated release PR requires a clean working tree to accurately detect the last release tag, generate the changelog, and synchronize version metadata without conflicts.

Why does automated version synchronization require GitHub authentication?

Automated version synchronization requires GitHub authentication to securely access repository history, collect merged PR changes, and open the release PR programmatically on behalf of the user.