メニュー
Prepare and cut an IronFlow release through develop and main, including PR resolution, integration validation, versioning, and tagging.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/skitsanos/ironflow --skill release-workflowコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Run IronFlow's Rust, policy, documentation, Lua-example, feature, audit, and optional live-storage validation. Use when the user asks to check, validate, lint, test, verify, audit, or confirm that an IronFlow change is ready. Do not modify failures unless the user also asks for fixes.
Implement one tracked IronFlow `IF-NNN` finding end to end across Rust code, tests, documentation, and Lua examples. Use when the user says to proceed with, fix, resolve, continue, or take the next IronFlow issue or development goal. Do not use for an untracked unrelated change unless the user asks to add it to the issue ledger.
Prepare, verify, version, and publish an IronFlow release from verified develop through a finalization branch to main. Use when the user asks to release, cut a release, ship a version, bump the version for release, or integrate dependency updates into a release. Do not use for routine dependency updates, PR review alone, or deployment without release intent.
SOC 職業分類に基づく
SKILL.md を表示中
| name | release-workflow |
| description | Prepare and cut an IronFlow release through develop and main, including PR resolution, integration validation, versioning, and tagging. |
Use explicit user approval before merging, closing remote PRs, committing, pushing, tagging, or publishing. Never force-push or delete a remote tag.
develop is the integration branch and uses X.Y.Z-dev.N.develop must use a version newer than remote develop in both
Cargo.toml and Cargo.lock.main is the release branch and uses stable X.Y.Z.vX.Y.Z tags on commits reachable from main.Use bun run scripts/development_version.ts bump <major|minor|patch|next> to
prepare a development version. next advances an existing candidate.
origin/develop and origin/main.develop with mergeability, review, and CI.
Before pushing, merge it, close it, or integrate its work and close it.
Request approval before any remote mutation.IF-NNN entries.X.Y.Z-dev.N, commit both version files, and run
scripts/integration_gate.sh..githooks/pre-push independently checks
incoming PRs, cleanliness, remote ancestry, development version, and the
full integration gate.develop CI is green.release/X.Y.Z from that exact develop commit. Never put a stable
version on develop.bun run scripts/development_version.ts finalize, then rerun
scripts/integration_gate.sh and commit only the finalization change.release/X.Y.Z to main, wait for required review, and merge using
repository policy. The resulting main push runs CI.main, create an annotated vX.Y.Z, prove it is
reachable from main, and prove its manifest version matches the tag.If a pushed tag is wrong, stop and request direction. Do not rewrite published history or delete remote tags automatically.