메뉴
Use when publishing a new version of the plugin.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | releasing |
| description | Use when publishing a new version of the plugin. |
Bump versions, tag, and publish a GitHub Release with an auto-generated changelog. All version sources must stay in sync.
| File | Field |
|---|---|
.claude-plugin/plugin.json | version |
.claude-plugin/marketplace.json | plugins[0].version |
| Git tag | vX.Y.Z |
Check commits since last tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Apply semver: patch for fixes, minor for features, major for breaking changes.
Group commits by type when there are enough to justify it:
feat:)fix:)refactor:)For small releases (< 5 commits), a flat list is fine.
The script pushes to origin and creates a public GitHub Release — irreversible. First show the user the final version number and the full changelog text, and get explicit approval before running it. Do not invoke the script autonomously.
After approval, run the release script:
${CLAUDE_PLUGIN_ROOT}/scripts/release.sh "<version>" "<changelog>"
This handles all mechanical steps: update both JSONs → commit → tag → push → create GitHub Release.
| Condition | Handling |
|---|---|
git describe fails (no prior tag) | First release — pick an initial version (e.g. 0.1.0); changelog from full git log --oneline |
gh not authenticated | Stop; ask the user to run gh auth login before retrying |
| Script fails mid-run | Inspect what completed (git tag, gh release list); finish remaining steps manually, don't re-run the whole script |
| Mistake | Fix |
|---|---|
| marketplace.json version not updated | Always update both JSON files together |
| Tag created before commit pushed | Push commit first, then tag, or use --tags |
| Changelog missing commits | Use prev_tag..HEAD, not prev_tag..new_tag before tagging |
Use when designing complex multi-step features, building new components, or planning significant behavior changes that require design exploration before implementation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when refining design docs and specs through deep questioning. Triggered when user says "help me refine this plan", "ask me about the project", "deep interview", or after brainstorming produces a design doc.
Use when implementing any feature or bugfix, before writing implementation code
Use when delegating coding work — prototyping, debugging, analysis, review, implementation, or generating publication-quality scientific/architecture diagrams — to Codex CLI. Supports multi-turn sessions via SESSION_ID.
Use when starting complex multi-step tasks, research projects, or anything needing >5 tool calls. Provides the persistent .planning/ directory used as on-disk working memory across sessions.