メニュー
Automate version release publication for the kit by validating `VERSION`, changelog files in `changelogs/`, tags, and GitHub release creation. Use when preparing or publishing a kit release.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/AlexAgo83/cdx-logics-kit --skill logics-version-release-managerコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Lint and validate the Logics Markdown conventions. Use when Codex should verify filenames, top headings, and required indicators across `logics/request`, `logics/backlog`, `logics/tasks`, `logics/product`, and `logics/architecture`, and report inconsistencies.
Update Logics indicators consistently. Use when Codex should update request/backlog/task indicators (`From version`, `Understanding`, `Confidence`, `Progress`, `Complexity`, `Theme`) or companion doc indicators in `logics/product|architecture/*.md` such as `Date`, `Status`, `Drivers`, related refs, and `Reminder`.
Manage this repository's Logics workflow (logics/request -> logics/backlog -> logics/tasks) and keep companion product or architecture refs aligned: create new request/backlog/task docs, promote between stages, keep From version, Understanding, Confidence, and Progress indicators consistent, and generate correctly-numbered filenames. Use when a user asks to triage an idea, write a request, promote it to a backlog item, or create an executable task plan.
SOC 職業分類に基づく
| name | logics-version-release-manager |
| description | Automate version release publication for the kit by validating `VERSION`, changelog files in `changelogs/`, tags, and GitHub release creation. Use when preparing or publishing a kit release. |
Use this skill to validate release inputs and publish a GitHub release from a versioned changelog.
The canonical version lives in VERSION.
The release notes source of truth lives in changelogs/CHANGELOGS_<version>.md.
python logics-version-release-manager/scripts/publish_version_release.py --dry-run
python logics-version-release-manager/scripts/publish_version_release.py --create-tag --push
flow assist prepare-release is the preferred end-to-end release helper. It chains release-changelog-status, validation-checklist, and diff-risk checks before invoking the publish script:
# Check readiness only (default suggestion-only mode)
python logics/skills/logics.py flow assist prepare-release --format json
# Dry-run the publish commands without executing them
python logics/skills/logics.py flow assist prepare-release --execution-mode execute --dry-run --format json
# Publish: create tag, push, and create GitHub release
python logics/skills/logics.py flow assist prepare-release --execution-mode execute --push --format json
# Publish as a draft release
python logics/skills/logics.py flow assist prepare-release --execution-mode execute --push --draft --format json
The ready key in the JSON output is true only when the curated changelog exists and the working tree is clean. The publish script is not invoked when ready is false.
python logics/skills/logics.py flow assist release-changelog-status --format json
python logics/skills/logics.py flow assist commit-all
VERSION by default; override with --version X.Y.Z.changelogs/.main and the tag, then publish the GitHub release via gh.flow assist prepare-release is the preferred release helper; the publish script itself stays deterministic.