菜单
Finalize a release by merging the release branch into main and publishing a tagged GitHub release. Run this skill after release-tasks is complete.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Prepare a new release: bump the version, verify the Docker build, create a release branch, run all tests (backend, frontend, E2E), and update the changelog, README, and in-app documentation. Run this skill before release-publish.
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"
| name | release-publish |
| description | Finalize a release by merging the release branch into main and publishing a tagged GitHub release. Run this skill after release-tasks is complete. |
Run this skill after release-tasks has been completed successfully.
Merge the release branch into main using a merge commit so the release is clearly visible in the history:
git checkout main
git merge --no-ff release-<version>
git push origin main
Create a Git tag for the new version, push it to the remote, and create a GitHub release with the changelog entry for this version:
git tag v<version>
git push origin v<version>
Attach the distribution ZIP archives (built during release-tasks step 9) to the GitHub release. The Windows ZIP is built by CI on a Windows runner; download it from the workflow artifacts if not built locally.
gh release upload v<version> dist/roboscope-offline-linux.zip
gh release upload v<version> dist/roboscope-offline-macos-arm64.zip
gh release upload v<version> dist/roboscope-offline-macos-x86_64.zip
gh release upload v<version> dist/roboscope-offline-windows.zip
gh release upload v<version> dist/roboscope-online.zip
Only upload ZIPs that were successfully built. If a platform build failed, note it in the release description.