Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/UfoMiao/zcf --skill zcf-releaseThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Showing SKILL.md
| name | zcf-release |
| description | Automate version release and code commit using changeset |
| disable-model-invocation | true |
| allowed-tools | Read(**), Exec(git, pnpm, node, date, cat, gh) |
Automate version release and code commit using changeset.
/zcf-release [-p|-mi|-ma|<version>]
-p or --patch: Patch version (default) - bug fixes, minor changes-mi or --minor: Minor version - new features, backward compatible-ma or --major: Major version - breaking changes, incompatible<version>: Specific version number (e.g., 1.2.3, 2.0.0-beta.1) - directly use provided versionYou are a professional release management assistant responsible for:
Parse arguments: $ARGUMENTS
VERSION_TYPE="patch" # Default to patch version
SPECIFIC_VERSION="" # For user-specified exact version
# Check if argument looks like a version number (matches semver pattern)
if [[ "$ARGUMENTS" =~ ^[0-9]+\.[0-9]+\.[0-9]+([.-].*)?$ ]]; then
SPECIFIC_VERSION="$ARGUMENTS"
VERSION_TYPE="custom"
echo "๐ Preparing to release exact version: $SPECIFIC_VERSION"
else
case "$ARGUMENTS" in
-p|--patch)
VERSION_TYPE="patch"
;;
-mi|--minor)
VERSION_TYPE="minor"
;;
-ma|--major)
VERSION_TYPE="major"
;;
"")
VERSION_TYPE="patch"
;;
*)
echo "โ Unknown parameter: $ARGUMENTS"
echo "Usage: /zcf-release [-p|-mi|-ma|<version>]"
echo "Examples:"
echo " /zcf-release -p # Patch version bump"
echo " /zcf-release -mi # Minor version bump"
echo " /zcf-release -ma # Major version bump"
echo " /zcf-release 1.2.3 # Exact version"
echo " /zcf-release 2.0.0-beta.1 # Pre-release version"
exit 1
;;
esac
echo "๐ Preparing to release $VERSION_TYPE version"
fi
Check if the current working directory meets release conditions:
# Ensure in project root directory
if [ ! -f "package.json" ]; then
echo "โ Error: package.json not found, please run in project root"
exit 1
fi
# Check for uncommitted changes and handle automatically
HAS_UNCOMMITTED=false
if ! git diff --quiet || ! git diff --cached --quiet; then
echo "โ ๏ธ Detected uncommitted changes:"
git status --short
echo ""
HAS_UNCOMMITTED=true
fi
echo "โ
Working directory status OK"
Analyze all changes since last release:
# Get last release tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$LAST_TAG" ]; then
echo "๐ No previous version tag found, analyzing all commits"
COMMITS=$(git log --oneline)
else
echo "๐ Last version: $LAST_TAG"
echo "Analyzing changes since $LAST_TAG..."
COMMITS=$(git log $LAST_TAG..HEAD --oneline)
fi
# Show commit history
echo -e "\n๐ Changes:"
echo "$COMMITS"
# Analyze file changes
echo -e "\n๐ File change statistics:"
if [ -z "$LAST_TAG" ]; then
git diff --stat
else
git diff --stat $LAST_TAG..HEAD
fi
Based on code change analysis, I will generate CHANGELOG following these standards:
Format Requirements:
Example Format:
## New Features
- Add technical execution guidelines with command best practices
- Support automated release command /zcf-release
- Automatic quote handling for Windows paths
## ๆฐๅ่ฝ
- ๆทปๅ ๆๆฏๆง่กๆๅๆๆกฃ๏ผๆไพๅฝไปคๆง่กๆไฝณๅฎ่ทต
- ๆฏๆ่ชๅจๅๅ็ๅฝไปค /zcf-release
- Windows ่ทฏๅพ่ชๅจๅ ๅผๅทๅค็
## Optimization
- Prioritize ripgrep for better search performance
- Improve template file organization
## ไผๅ
- ไผๅ
ไฝฟ็จ ripgrep ๆๅๆ็ดขๆง่ฝ
- ๆน่ฟๆจกๆฟๆไปถ็ป็ป็ปๆ
## Fixes
- Fix Windows path backslash escaping issue
## ไฟฎๅค
- ไฟฎๅค Windows ่ทฏๅพๅๆๆ ไธขๅคฑ้ฎ้ข
Create changeset file based on analysis:
# Generate timestamp
TIMESTAMP=$(date +%Y%m%d%H%M%S)
CHANGESET_FILE=".changeset/release-$TIMESTAMP.md"
# Create changeset file
echo "๐ Creating changeset file..."
if [ "$VERSION_TYPE" = "custom" ]; then
# For specific version, use the exact version number
cat > "$CHANGESET_FILE" << EOF
---
"zcf": $SPECIFIC_VERSION
---
[Bilingual CHANGELOG content generated based on actual changes]
EOF
echo "โ
Changeset file created with exact version: $SPECIFIC_VERSION"
else
# For version type (patch/minor/major), use the type
cat > "$CHANGESET_FILE" << EOF
---
"zcf": $VERSION_TYPE
---
[Bilingual CHANGELOG content generated based on actual changes]
EOF
echo "โ
Changeset file created with version type: $VERSION_TYPE"
fi
Use changeset to update version number and CHANGELOG:
echo "๐ Updating version number and CHANGELOG..."
pnpm changeset version
# Note: The changeset version command will automatically:
# 1. Update package.json version
# 2. Generate/update CHANGELOG.md
# 3. DELETE the temporary changeset file in .changeset/ directory
# No manual cleanup needed!
# Get new version number
NEW_VERSION=$(node -p "require('./package.json').version")
if [ "$VERSION_TYPE" = "custom" ]; then
echo "๐ฆ New version set to: v$NEW_VERSION (specified: $SPECIFIC_VERSION)"
else
echo "๐ฆ New version: v$NEW_VERSION"
fi
# Show CHANGELOG update
echo -e "\n๐ CHANGELOG has been updated, please review the content"
echo "โ
Temporary changeset file has been automatically deleted"
Create release branch first, then handle commits separately to avoid polluting main branch:
echo "๐ Creating release branch..."
# Create and switch to release branch
RELEASE_BRANCH="release/v$NEW_VERSION"
git checkout -b "$RELEASE_BRANCH"
# Handle uncommitted changes first (if any)
if [ "$HAS_UNCOMMITTED" = true ]; then
echo "๐ Committing pre-release changes..."
# Stage only the uncommitted changes (exclude changeset modifications)
git add .
git reset HEAD package.json CHANGELOG.md 2>/dev/null || true
# Check if there are still changes to commit after reset
if ! git diff --quiet --staged; then
# Analyze the staged changes to generate appropriate commit message
echo "๐ Analyzing uncommitted changes..."
CHANGED_FILES=$(git diff --staged --name-only)
# Generate commit message based on changed files
COMMIT_TYPE="chore"
COMMIT_SCOPE=""
COMMIT_DESCRIPTION="pre-release changes"
# Analyze file patterns to determine commit type and scope
if echo "$CHANGED_FILES" | grep -E "\.(md|txt)$" >/dev/null; then
if echo "$CHANGED_FILES" | grep -i "readme" >/dev/null; then
COMMIT_TYPE="docs"
COMMIT_SCOPE="readme"
COMMIT_DESCRIPTION="update README documentation"
elif echo "$CHANGED_FILES" | grep -E "\.claude/" >/dev/null; then
COMMIT_TYPE="docs"
COMMIT_SCOPE="commands"
COMMIT_DESCRIPTION="update command documentation"
else
COMMIT_TYPE="docs"
COMMIT_DESCRIPTION="update documentation"
fi
elif echo "$CHANGED_FILES" | grep -E "\.(ts|js|tsx|jsx)$" >/dev/null; then
if echo "$CHANGED_FILES" | grep -E "test|spec" >/dev/null; then
COMMIT_TYPE="test"
COMMIT_DESCRIPTION="update tests"
else
COMMIT_TYPE="feat"
COMMIT_DESCRIPTION="code changes"
fi
elif echo "$CHANGED_FILES" | grep -E "\.json$" >/dev/null; then
if echo "$CHANGED_FILES" | grep "package" >/dev/null; then
COMMIT_TYPE="chore"
COMMIT_DESCRIPTION="update dependencies"
else
COMMIT_TYPE="chore"
COMMIT_DESCRIPTION="update configuration"
fi
fi
# Build commit message
if [ -n "$COMMIT_SCOPE" ]; then
COMMIT_MSG="${COMMIT_TYPE}(${COMMIT_SCOPE}): ${COMMIT_DESCRIPTION}"
else
COMMIT_MSG="${COMMIT_TYPE}: ${COMMIT_DESCRIPTION}"
fi
# Add file list to commit body
COMMIT_BODY=""
for file in $CHANGED_FILES; do
COMMIT_BODY="${COMMIT_BODY}- Update ${file}
"
done
COMMIT_BODY="${COMMIT_BODY}
๐ค Generated with [Claude Code](https://claude.ai/code)
# Create the commit
git commit -m "${COMMIT_MSG}
${COMMIT_BODY}"
echo "โ
Pre-release changes committed: $COMMIT_MSG"
else
echo "โน๏ธ No additional changes to commit after version update"
fi
fi
echo "๐พ Committing release version changes..."
# Add version-related changes
git add package.json CHANGELOG.md
# Create release version commit
git commit -m "chore: release v$NEW_VERSION
- Update version to $NEW_VERSION
- Update CHANGELOG.md
- Generated by /zcf-release command"
# Push release branch to remote and set upstream tracking
git push -u origin "$RELEASE_BRANCH"
# If push fails due to conflicts, use force-with-lease to safely overwrite
# git push --force-with-lease origin "$RELEASE_BRANCH"
# Set upstream tracking if not set automatically
git branch --set-upstream-to=origin/$RELEASE_BRANCH $RELEASE_BRANCH
### 8. Create Pull Request
```bash
echo "๐ Creating pull request..."
# Create pull request using gh CLI following the project's PR template
gh pr create --title "๐ Release v$NEW_VERSION" --body "$(cat <<'EOF'
## Description
Release version v$NEW_VERSION with automated version bump and CHANGELOG update.
This release includes important changes, please review CHANGELOG.md for details.
## Type of Change
- [x] New feature
- [ ] Bug fix
- [ ] Breaking change
- [x] Documentation update
## Testing
- [x] Tests added/updated
- [x] All tests pass
- [x] Coverage maintained
## Checklist
- [x] Code follows style guidelines
- [x] Self-review completed
- [x] Documentation updated
- [x] No new warnings introduced
## Release Notes
โ ๏ธ **IMPORTANT**: After merge, GitHub Actions will automatically:
- Create release tag
- Publish to npm
- Generate GitHub Release
๐ค Generated by /zcf-release command
EOF
)"
echo -e "\nโ
Release preparation complete!"
echo "๐ฆ Version v$NEW_VERSION is ready"
echo "๐ Pull request created successfully"
echo ""
echo "โ ๏ธ IMPORTANT: Review and merge the PR to trigger the release"
echo "โ ๏ธ Do NOT create or push tags manually!"
echo "๐ค After PR merge, GitHub Actions will automatically:"
echo " - Create the release tag"
echo " - Publish to npm"
echo " - Generate GitHub Release"
echo "๐ View release status: https://github.com/UfoMiao/zcf/actions"
โ ๏ธ CRITICAL: NEVER create or push Git tags manually! GitHub Actions will automatically:
Manual tags will cause conflicts with the automated release process!
release/v{version} branchchangeset version automatically deletes temporary changeset files.changeset/ directory should only contain config files, not temporary release filesgh CLI: Ensure GitHub CLI is installed and authenticated for PR creationVersion Parameter Examples:
/zcf-release or /zcf-release -p - Auto patch bump (2.9.11 โ 2.9.12)/zcf-release -mi - Auto minor bump (2.9.11 โ 2.10.0)/zcf-release -ma - Auto major bump (2.9.11 โ 3.0.0)/zcf-release 1.5.0 - Exact version (โ 1.5.0)/zcf-release 3.0.0-alpha.1 - Pre-release version (โ 3.0.0-alpha.1)Now starting release process...