一键导入
release
Use when creating a tagged release with changelog. Triggers on "release", "tag a release", "cut a release", or when ready to publish a new version.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when creating a tagged release with changelog. Triggers on "release", "tag a release", "cut a release", or when ready to publish a new version.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when adding a new transform effect, creating a post-process shader, or planning effect implementation. Provides the complete checklist of files and commonly-missed steps.
Use when exploring a vague idea, finding inspiration, or researching a technique before planning. Triggers on "I want to add...", "what if...", "research", "look up", or when uncertain about what to build.
Use when creating a git commit for staged or unstaged changes. Triggers on "commit this", "save my changes", or when implementation work completes and needs version control.
Use when reviewing an implemented feature against its plan document. Triggers after implementation completes, on "review this", or when checking if code matches specification.
Use when planning a new feature before implementation. Triggers on "plan", "design", "architect", or when describing a feature to build.
Use when executing a feature plan with wave-based parallel agents. Triggers on "implement this plan", "start building", or when a plan exists in docs/plans/ and user wants to begin coding.
| name | release |
| description | Use when creating a tagged release with changelog. Triggers on "release", "tag a release", "cut a release", or when ready to publish a new version. |
Draft a changelog entry, commit it, and tag locally. User pushes when ready.
Goal: Understand what changed since the last release
Actions:
git describe --tags --abbrev=0 2>/dev/null
git log)git log <last-tag>..HEAD (full messages, no format flags)STOP: If there are zero new commits since the last tag, tell user there's nothing to release.
Goal: Write a concise, user-facing changelog entry
Actions:
STOP: Wait for user approval or edits before proceeding.
Goal: Propose a fun ALL-CAPS tag name
Actions:
STOP: Wait for user to confirm the tag name.
Goal: Create or update the changelog file
Actions:
CHANGELOG.md doesn't exist: create it with header # Changelog followed by the new entry# Changelog header, above existing entries## YYYY-MM-DD — TAG-NAME
### New Effects
- ...
### Enhancements
- ...
### Fixes
- ...
CHANGELOG.mdGoal: Record the changelog and create the tag
Actions:
CHANGELOG.md with message: Add TAG-NAME changelog entrygit tag -a TAG-NAME -m "TAG-NAME"
TAG-NAME locally"git push origin main && git push origin TAG-NAME"| Thought | Reality |
|---|---|
| "I'll list every commit" | One bullet per distinct feature, not per commit. |
| "I'll push the tag for them" | Tag locally. User pushes. |
| "This refactor is worth mentioning" | User-facing changes only. |
| "No commits since last tag" | Nothing to release. Tell user and stop. |
| "I'll pick the tag name myself" | Suggest options. User decides. |
| "This new effect had a follow-up fix - I'll list both" | New effects cannot have fixes in the same release. Drop the fix bullet. |