Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送".

Release Skills Universal release workflow supporting any project type with multi language changelog. Quick Start Just run /release skills auto detects your project configuration. Supported Projects Project Type Version File Auto Detected Node.js package.json ✓ Python pyproject.toml ✓ Rust Cargo.toml ✓ Claude Plugin marketplace.json ✓ Generic VERSION / version.txt ✓ Options Flag Description dry run Preview changes without executing major Force major version bump minor Force minor version bump patch Force patch version bump Workflow Step 1: Detect Project Configuration 1. Check for .releaserc.yml (optional config override) 2. Auto detect version file by scanning (priority order): package.json (Node.js) pyproject.toml (Python) Cargo.toml (Rust) marketplace.json or .claude plugin/marketplace.json (Claude Plugin) VERSION or version.txt (Generic) 3. Scan for changelog files using glob patterns: CHANGELOG .md HISTORY .md CHANGES .md 4. Identify language of each changelog by filename suffix 5. Display detected configuration Language Detection Rules : Filename Pattern Language CHANGELOG.md (no suffix) en (default) CHANGELOG.zh.md / CHANGELOG CN.md / CHANGELOG.zh CN.md zh CHANGELOG.ja.md / CHANGELOG JP.md ja CHANGELOG.ko.md / CHANGELOG KR.md ko CHANGELOG.de.md / CHANGELOG DE.md de CHANGELOG.fr.md / CHANGELOG FR.md fr CHANGELOG.es.md / CHANGELOG ES.md es CHANGELOG.{lang}.md Corresponding language code Output Example : Step 2: Analyze Changes Since Last Tag Categorize by conventional commit types: Type Description feat New features fix Bug fixes docs Documentation refactor Code refactoring perf Performance improvements test Test changes style Formatting, styling chore Maintenance (skip in changelog) Breaking Change Detection : Commit message starts with BREAKING CHANGE Commit body/footer contains BREAKING CHANGE: Removed public APIs, renamed exports, changed interfaces If breaking changes detected, warn user: "Breaking changes detected. Consider major version bump ( major flag)." Step 3: Determine Version Bump Rules (in priority order): 1. User flag major/ minor/ patch → Use specified 2. BREAKING CHANGE detected → Major bump (1.x.x → 2.0.0) 3. feat: commits present → Minor bump (1.2.x → 1.3.0) 4. Otherwise → Patch bump (1.2.3 → 1.2.4) Display version change: 1.2.3 → 1.3.0 Step 4: Generate Multi language Changelogs For each detected changelog file: 1. Identify language from filename suffix 2. Detect third party contributors : Check merge commits: git log ${LAST TAG}..HEAD merges pretty=format:"%H %s" For each merged PR, identify the PR author via gh pr view <number json author jq '.author.login' Compare against repo owner ( gh repo view json owner jq '.owner.login' ) If PR author ≠ repo owner → third party contributor 3. Generate content in that language : Section titles in target language Change descriptions written naturally in target language (not translated) Date format: YYYY MM DD (universal) Third party contributions : Append contributor attribution (by @username) to the changelog entry 4. Insert at file head (preserve existing content) Section Title Translations (built in): Type en zh ja ko de fr es feat Features 新功能新機能 새로운 기능 Funktionen Fonctionnalités Características fix Fixes 修复修正 수정 Fehlerbehebungen Corrections Correcciones docs Documentation 文档ドキュメント 문서 Dokumentation Documentation Documentación refactor Refactor 重构リファクタリング 리팩토링 Refactoring Refactorisation Refactorización perf Performance 性能优化パフォーマンス 성능 Leistung Performance Rendimiento breaking Breaking Changes 破坏性变更破壊的変更 주요 변경사항 Breaking Changes Changements majeurs Cambios importantes Changelog Format : Only include sections that have changes. Omit empty sections. Third Party Attribution Rules : Only add (by @username) for contributors who are NOT the repo owner Use GitHub username with @ prefix Place at the end of the changelog entry line Apply to all languages consistently (always use (by @username) format, not translated) Multi language Example : English (CHANGELOG.md): Chinese (CHANGELOG.zh.md): Japanese (CHANGELOG.ja.md): Step 5: Group Changes by Skill/Module Analyze commits since last tag and group by affected skill/module: 1. Identify changed files per commit 2. Group by skill/module : skills/<skill name / → Group under that skill Root files (CLAUDE.md, etc.) → Group as "project" Multiple skills in one commit → Split into multiple groups 3. For each group , identify related README updates needed Example Grouping : Step 6: Commit Each Skill/Module Separately For each skill/module group (in order of changes): 1. Check README updates needed : Scan README .md for mentions of this skill/module Verify options/flags documented correctly Update usage examples if syntax changed Update feature descriptions if behavior changed 2. Stage and commit : 3. Commit message format : Use conventional commit format: <type (<scope ): <description <type : feat, fix, refactor, docs, perf, etc. <scope : skill name or "project" <description : Clear, meaningful description of changes Example Commits : Common README Updates Needed : Change Type README Section to Check New options/flags Options table, usage examples Renamed options Options table, usage examples New features Feature description, examples Breaking changes Migration notes, deprecation warnings Restructured internals Architecture section (if exposed to users) Step 7: Generate Changelog and Update Version 1. Generate multi language changelogs (as described in Step 4) 2. Update version file : Read version file (JSON/TOML/text) Update version number Write back (preserve formatting) Version Paths by File Type : File Path package.json $.version pyproject.toml project.version Cargo.toml package.version marketplace.json $.metadata.version VERSION / version.txt Direct content Step 8: User Confirmation Before creating the release commit, ask user to confirm: Use AskUserQuestion with two questions : 1. Version bump (single select): Show recommended version based on Step 3 analysis Options: recommended (with label), other semver options Example: 1.2.3 → 1.3.0 (Recommended) , 1.2.3 → 1.2.4 , 1.2.3 → 2.0.0 2. Push to remote (single select): Options: "Yes, push after commit", "No, keep local only" Example Output Before Confirmation : Step 9: Create Release Commit and Tag After user confirmation: 1. Stage version and changelog files : 2. Create release commit : 3. Create tag : 4. Push if user confirmed (Step 8): Note : Do NOT add Co Authored By line. This is a release commit, not a code contribution. Post Release Output : Configuration (.releaserc.yml) Optional config file in project root to override defaults: Dry Run Mode When dry run is specified: Example Usage When to Use Trigger this skill when user requests: "release", "发布", "create release", "new version", "新版本" "bump version", "update version", "更新版本" "prepare release" "push to remote" (with uncommitted changes) Important : If user says "just push" or "直接 push" with uncommitted changes, STILL follow all steps above first.

release-skills