Release Skills

Release Skills

Universal release workflow supporting any project type with multi-language changelog generation.

Supported Projects

TypeVersion FileAuto-DetectedNode.jspackage.json✓Pythonpyproject.toml✓RustCargo.toml✓Claude Pluginmarketplace.json✓GenericVERSION / version.txt✓

Options

FlagDescription--dry-runPreview changes without executing--majorForce major version bump--minorForce minor version bump--patchForce patch version bump

Step 1: Detect Configuration

Check for .releaserc.yml (optional config) Auto-detect version file (priority: package.json → pyproject.toml → Cargo.toml → marketplace.json → VERSION) Scan for changelog files: CHANGELOG*.md, HISTORY*.md, CHANGES*.md Identify language of each changelog by suffix Language Detection: PatternLanguageCHANGELOG.md (no suffix)enCHANGELOG.zh.md / CHANGELOG_CN.mdzhCHANGELOG.ja.md / CHANGELOG_JP.mdjaCHANGELOG.{lang}.mdCorresponding language Output: Project detected: Version file: package.json (1.2.3) Changelogs: CHANGELOG.md (en), CHANGELOG.zh.md (zh)

Step 2: Analyze Changes

LAST_TAG=$(git tag --sort=-v:refname | head -1) git log ${LAST_TAG}..HEAD --oneline Categorize by conventional commit: feat: → Features fix: → Fixes docs: → Documentation refactor: → Refactor perf: → Performance chore: → Skip in changelog Breaking Change Detection: BREAKING CHANGE in message or body Removed public APIs, renamed exports Warn if breaking changes: "Consider major version bump (--major)."

Step 3: Determine Version

Priority: User flag (--major/--minor/--patch) BREAKING CHANGE → Major (1.x.x → 2.0.0) feat: present → Minor (1.2.x → 1.3.0) Otherwise → Patch (1.2.3 → 1.2.4) Display: 1.2.3 → 1.3.0

Step 4: Generate Changelogs

• For each changelog file:
• Identify language from filename
• Detect third-party contributors via merged PRs
• Generate content in that language:
• Section titles in target language
• Date format: YYYY-MM-DD
• Attribution: (by @username) for non-owner contributors
• Insert at file head, preserve existing content
• Section Titles:
• TypeenzhjafeatFeatures新功能新機能fixFixes修复修正docsDocumentation文档ドキュメントbreakingBreaking Changes破坏性变更破壊的変更
• Format:
• ## 1.3.0 - 2026-01-22
• ### Features
• Add user authentication (by @contributor1)
• Support OAuth2 login
• ### Fixes
• Fix memory leak in connection pool

Step 5: Group by Module (Optional)

For monorepos, group commits by affected skill/module: baoyu-cover-image: - feat: add new style options → README updates: options table baoyu-comic: - refactor: improve panel layout → No README updates

Step 6: User Confirmation

Present: Changelog preview Proposed version bump Changes summary Ask: Confirm version bump (show recommended) Push to remote? (Yes/No)

Step 7: Create Release

# Stage files git add <version-file> CHANGELOG*.md # Commit git commit -m "chore: release v{VERSION}" # Tag git tag v{VERSION} # Push (if confirmed) git push origin main git push origin v{VERSION} Output: Release v1.3.0 created. Tag: v1.3.0 Status: Pushed to origin

Scripts

ScriptPurposescripts/prepare_release.pyPrepare release with version bumpscripts/release_notes.pyGenerate release notes from commitsscripts/roadmap_changelog.pyGenerate changelog from roadmap

Configuration (.releaserc.yml)

Optional overrides: version: file: package.json path: $.version changelog: files: - path: CHANGELOG.md lang: en - path: CHANGELOG.zh.md lang: zh commit: message: "chore: release v{version}" tag: prefix: v

Dry-Run Mode

With --dry-run: Show all proposed changes Preview changelog entries List commits to create No actual changes made

Version Paths

FilePathpackage.json$.versionpyproject.tomlproject.versionCargo.tomlpackage.versionmarketplace.json$.metadata.versionVERSIONDirect content

Quality Criteria

Good releases: Clear changelog entries describing user-facing changes Proper contributor attribution Consistent multi-language content No orphaned tags (always with commit) Version bump matches change significance

NEVER

Force push to main/master Skip user confirmation before push Create tags without commits Include internal/chore changes in user-facing changelog Push without explicit user consent Add Co-Authored-By to release commits (they're automated)