Agent Skills › Houseofmvps/ultraship › release

release

GitHub

执行完整的软件发布流程，包括基于提交记录生成变更日志、确定语义化版本升级、更新版本号、创建Git标签、发布GitHub Release及npm包。

skills/release/SKILL.md Houseofmvps/ultraship

Trigger Scenarios

用户请求发布新版本用户要求发布到npm 用户希望生成发布说明

Install

npx skills add Houseofmvps/ultraship --skill release -g -y

More Options

Use without installing

npx skills use Houseofmvps/ultraship@release

指定 Agent (Claude Code)

npx skills add Houseofmvps/ultraship --skill release -a claude-code -g -y

安装 repo 全部 skill

npx skills add Houseofmvps/ultraship --all -g -y

预览 repo 内 skill

npx skills add Houseofmvps/ultraship --list

SKILL.md

Frontmatter

{
    "name": "release",
    "description": "Generate changelog from commits, bump version, create GitHub release, publish to npm. Use when user wants to release, publish, or ship a new version.",
    "argument-hint": "<major|minor|patch>"
}

Release

Full release pipeline: changelog → version bump → commit → tag → GitHub release → npm publish.

Process

Step 1: Determine Version Bump

Check recent commits since last tag to determine semver bump:

git describe --tags --abbrev=0 2>/dev/null || echo "none"
git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --oneline

Analyze commit messages:

Any BREAKING CHANGE: or !: → major bump
Any feat: → minor bump
Only fix:, chore:, docs:, refactor: → patch bump

If the user specifies a version (e.g., "release 2.0.0"), use that instead.

Step 2: Generate Changelog

Group commits by type:

## What's New
- feat: Add deploy command with pre-flight checks
- feat: Add content scoring with readability analysis

## Bug Fixes
- fix: Secret scanner false positive on .env.example

## Other Changes
- chore: Update dependencies
- refactor: Restructure SEO scanner for cross-page analysis

Step 3: Version Bump

Update version in:

package.json — the version field
Any other version references the project uses

# Read current version
node -e "console.log(JSON.parse(require('fs').readFileSync('package.json','utf8')).version)"

Use the Edit tool to update the version string.

Step 4: Commit & Tag

git add package.json CHANGELOG.md
git commit -m "release: v<new-version>"
git tag -a v<new-version> -m "v<new-version>"

Step 5: Push

git push origin main --tags

Step 6: GitHub Release

gh release create v<new-version> --title "v<new-version>" --notes "<changelog>"

Use the changelog from Step 2 as release notes.

Step 7: npm Publish (if applicable)

Only if package.json exists and has a name field (and is not private):

npm publish

If publish fails due to auth, show the user how to set up their npm token.

Step 8: Post-Release Summary

====================================
  RELEASE COMPLETE
====================================
  Package:    ultraship
  Version:    1.0.7
  Tag:        v1.0.7
  Commits:    12 since last release
  GitHub:     https://github.com/Houseofmvps/ultraship/releases/tag/v1.0.7
  npm:        https://www.npmjs.com/package/ultraship
====================================
  Changelog:
  - 3 new features
  - 2 bug fixes
  - 1 breaking change
====================================