release-skills

Detect version files and changelogs to prepare releases across multi-language projects.

24.8k|2.8k|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/JimLiu/baoyu-skills --skill release-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-skills
Source: https://github.com/JimLiu/baoyu-skills/tree/main/.claude/skills/release-skills
Command: npx skills add https://github.com/JimLiu/baoyu-skills --skill release-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The universal release workflow automates cross-project release planning by auto-detecting version files and changelogs across Node.js, Python, Rust, Claude Plugin, and generic projects.

Core Features & Use Cases

  • Auto-detect project configuration to determine current version and changelog locations.
  • Determine appropriate version bumps (major/minor/patch) based on user input and commit history.
  • Generate multi-language changelogs and prepare release commits and tags for multilingual projects.

Quick Start

Run the release-skills command to automatically detect your project's release configuration and prepare a release plan.

Frequently Asked Questions about release-skills

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

FAQPage Schema
How do I automate version bumps and changelog generation for a multi-language project?

To automate version bumps and changelog generation for multi-language projects, this Skill scans version files and applies conventional commit rules to determine major, minor, or patch bumps. It structures multilingual changelogs and prepares release commits automatically.

Can I use a universal release workflow for both Node.js and Python projects?

Yes, you can use this universal release workflow for Node.js, Python, Rust, and Claude Plugin projects. It auto-detects project configurations to identify current version locations and manage releases across these environments.

How does auto-detect work when scanning version files and changelogs?

Auto-detect works by scanning your project directory to locate configuration files, identifying the latest version numbers and existing changelogs. It then resolves appropriate version bumps by analyzing commit history with conventional rules.

What's the best way to prepare a release commit across different programming languages?

The best way to prepare a release commit across different languages is to run the auto-detect workflow. It identifies your project type, resolves the correct version bump, generates the appropriate multilingual changelog, and structures the final release commit and tags.

Do I need to manually configure versioning rules for conventional commits?

No, you do not need to manually configure versioning rules. The workflow automatically resolves version bump decisions by applying conventional commit rules directly to your commit history during the release preparation process.

Why does my multi-language changelog generation not reflect recent commit history?

If your multilingual changelog generation does not reflect recent commits, it may be due to non-conventional commit messages that the auto-detect rules cannot parse, or the project configuration was not properly identified during the initial directory scan.