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

CHANGELOG.md

CHANGELOG.zh.md

CHANGELOG_CN.md

CHANGELOG.zh-CN.md

CHANGELOG.ja.md

CHANGELOG_JP.md

CHANGELOG.ko.md

CHANGELOG_KR.md

CHANGELOG.de.md

CHANGELOG_DE.md

CHANGELOG.fr.md

CHANGELOG_FR.md

CHANGELOG.es.md

CHANGELOG_ES.md

CHANGELOG.{lang}.md

Project detected:
  Version file: package.json (1.2.3)
  Changelogs:
    - CHANGELOG.md (en)
    - CHANGELOG.zh.md (zh)
    - CHANGELOG.ja.md (ja)

LAST_TAG=$(git tag --sort=-v:refname | head -1)
git log ${LAST_TAG}..HEAD --oneline
git diff ${LAST_TAG}..HEAD --stat

• Commit message starts with

  BREAKING CHANGE

• Commit body/footer contains

  BREAKING CHANGE:

• Removed public APIs, renamed exports, changed interfaces

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)

1.2.3 → 1.3.0

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)

undefined

• Description of new feature
• Description of third-party contribution (by @username)

• Description of fix

• Description of docs changes

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):
```markdown

• Add user authentication module (by @contributor1)
• Support OAuth2 login

• Fix memory leak in connection pool

Chinese (CHANGELOG.zh.md):
```markdown

• 新增用户认证模块 (by @contributor1)
• 支持 OAuth2 登录

• 修复连接池内存泄漏问题

Japanese (CHANGELOG.ja.md):
```markdown

• ユーザー認証モジュールを追加 (by @contributor1)
• OAuth2 ログインをサポート

• コネクションプールのメモリリークを修正

undefined

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

tuzi-cover-image:
  - feat: add new style options
  - fix: handle transparent backgrounds
  → README updates: options table

tuzi-comic:
  - refactor: improve panel layout algorithm
  → No README updates needed

project:
  - docs: update CLAUDE.md architecture section

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:
   bash

   git add skills/<skill-name>/*
   git add README.md README.zh.md  # If updated for this skill
   git commit -m "<type>(<skill-name>): <meaningful description>"

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

git commit -m "feat(tuzi-cover-image): add watercolor and minimalist styles"
git commit -m "fix(tuzi-comic): improve panel layout for long dialogues"
git commit -m "docs(project): update architecture documentation"

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

project.version

package.version

$.metadata.version

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"

Commits created:
  1. feat(tuzi-cover-image): add watercolor and minimalist styles
  2. fix(tuzi-comic): improve panel layout for long dialogues
  3. docs(project): update architecture documentation

Changelog preview (en):
  ## 1.3.0 - 2026-01-22
  ### Features
  - Add watercolor and minimalist styles to cover-image
  ### Fixes
  - Improve panel layout for long dialogues in comic

Ready to create release commit and tag.

1. Stage version and changelog files:
   bash

   git add <version-file>
   git add CHANGELOG*.md

2. Create release commit:
   bash

   git commit -m "chore: release v{VERSION}"

3. Create tag:
   bash

   git tag v{VERSION}

4. Push if user confirmed (Step 8):
   bash

   git push origin main
   git push origin v{VERSION}

Release v1.3.0 created.

Commits:
  1. feat(tuzi-cover-image): add watercolor and minimalist styles
  2. fix(tuzi-comic): improve panel layout for long dialogues
  3. docs(project): update architecture documentation
  4. chore: release v1.3.0

Tag: v1.3.0
Status: Pushed to origin  # or "Local only - run git push when ready"

Section mapping (conventional commit type → changelog section)

Use null to skip a type in changelog

• README.md
• package.json

undefined

• "release", "发布", "create release", "new version", "新版本"
• "bump version", "update version", "更新版本"
• "prepare release"
• "push to remote" (with uncommitted changes)