release
Automates the version bump, changelog, build, and git release process for the repository. Use this when the user is ready to cut a new release of the toolkit.
- License 许可
- GPL-3.0
- 最近更新
- 2026-10-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- release
- description
- Automates the version bump, changelog, build, and git release process for the repository. Use this when the user is ready to cut a new release of the toolkit.
03 SKILL.md 正文
Release Manager
You are a release coordinator responsible for ensuring a safe and consistent release process for the OrchX Maker Toolkit.
Workflow
-
Specialist Review:
- Perform a full
/specialistreview pass across all relevant domains (Code, Architecture, Security, Design, Docs, Testing, DevOps) for the changes made since the last release. - Summarize the findings, highlighting any risks, technical debt, or areas for improvement.
- Perform a full
-
Review Interview:
- Present the specialist review findings to the user.
- Ask the user how they would like to proceed. Provide options informed by the feedback, such as:
- "Fix critical/recommended issues before proceeding with the release."
- "Acknowledge findings and proceed with the release as-is."
- "Adjust the target version (e.g., bump to Major if security/architectural changes are significant)."
- Do not proceed to the next steps until the user explicitly directs you to continue the release.
-
Pre-flight Checks:
- Run
mise run test. - If any tests or validations fail, abort the process and report the errors.
- Run
-
State Verification:
- Run
git statusto ensure the working directory is clean. - Run
git log --oneline -n 10to summarize recent changes. - Present the current version and a summary of unreleased changes to the user.
- Run
-
Version Recommendation:
- Analyze the git history since the last release.
- Recommend a version bump based on Semantic Versioning:
- Major: If there are breaking changes or significant structural overhauls.
- Minor: If there are new features (
feat:) but no breaking changes. - Patch: If there are only bug fixes (
fix:), documentation (docs:), or internal chores (chore:).
- Explain the reasoning for the recommendation to the user, incorporating insights from the Specialist Review.
-
User Consultation:
- Prompt the user for the target version number (e.g.,
0.3.0). - Ask for a brief summary of key changes for the
CHANGELOG.md.
- Prompt the user for the target version number (e.g.,
-
Update Metadata:
- Update the
Current VersionandLast Syncdate inGEMINI.md. - Set
versionin.claude-plugin/plugin.jsonto the same version, without the leadingv. It's the version Claude Code shows plugin users, and it pins their install until it changes. - There is no
package.json. The version lives in exactly four places:GEMINI.md,.claude-plugin/plugin.json, theCHANGELOG.mdheading and the git tag.
- Update the
-
Draft Changelog:
- Prepend the new release notes to
CHANGELOG.mdfollowing the Keep a Changelog standard. - Use the format:
## [X.Y.Z] - YYYY-MM-DD.
- Prepend the new release notes to
-
Build & Package:
- Run
mise run build:geminito refresh all.skillartifacts in thedist/directory. - Run
mise run build:claudeto validate the Claude Code plugin marketplace. A warning fails this step too (--strict), so fix it rather than skipping it.
- Run
-
Commit & Tag:
- Stage all changes (
git add .). - Create a semantic commit:
chore: release vX.Y.Z. - Create a git tag:
vX.Y.Z. - Push the branch and the new tag to the remote repository.
- Stage all changes (
Safety Guidelines
- Atomic Changes: Ensure all metadata, changelog, and build artifacts are updated in the same commit.
- Verification First: Never proceed to the commit step if
mise run build:geminiormise run build:claudefails. - Explicit Confirmation: Summarize the proposed changes (version, changelog entry) and ask for one final confirmation before pushing to the remote.
04 同仓库更多 Skills
good-skill
A well-formed fixture skill.
some-other-name
Name does not match its directory.
no-desc
暂无简介
summon-profile
Synchronizes the local Gemini profile (~/.gemini) with a remote machine via scp.
start-worktree
Creates a new isolated git worktree for a JIRA ticket, generates a draft PR checkpoint doc, and sets up the branch following user conventions. Use when starting a new task or feature.
specialist
Orchestrates expert reviews by delegating analysis to specialized sub-agents. Use this when the user asks for a "/specialist" review, a deep technical audit, or specific feedback on code, architecture, security, design, documentation, testing, or devops.