メニュー
Repo-local release workflow for this Ailtir plugin repository. Use when the user asks to bump the plugin version, update plugin/.claude-plugin/plugin.json, update CHANGELOG.md, create the version bump commit, and tag that version commit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | bump-the-version |
| description | Repo-local release workflow for this Ailtir plugin repository. Use when the user asks to bump the plugin version, update plugin/.claude-plugin/plugin.json, update CHANGELOG.md, create the version bump commit, and tag that version commit. |
Use scripts/bump_version.py from this skill. Run it from the repository root.
python3 .codex/skills/bump-the-version/scripts/bump_version.py 2.10.2 \
--note "Fixed telemetry reporting when Claude invokes plugin helper scripts by absolute path."
The script performs the repo-specific release sequence:
plugin/.claude-plugin/plugin.json.CHANGELOG.md.Bump version to X.Y.Z.vX.Y.Z.pending marker with the version commit hash.Update changelog version reference.The tag must point to the version bump commit, not the changelog-reference follow-up commit.
Pass one or more --note values when the release has specific user-visible
changes:
python3 .codex/skills/bump-the-version/scripts/bump_version.py 2.10.2 \
--note "Fixed telemetry reporting for installed plugin helpers." \
--note "Kept plugin runtime variables out of user-facing configuration."
If the user only asks for a version bump and gives no release-note text, let the script use its default note. Do not invent detailed release notes without inspecting the commits since the previous version.
The script creates local commits and a local tag by default. If the user asks to push too, run:
git push
git push origin vX.Y.Z
Do not use git push --tags unless the user explicitly asks to push every local
tag.
Compiles the final submission documents. Triggered by /ailtir-cowork-plugin:ailtir_bid-assembly.
Phase 2 skill. Compares received subcontractor quotes for a specific trade package. Normalises pricing, scopes, and exclusions into a multi-tab Excel comparison. Triggered by /ailtir-cowork-plugin:ailtir_bid-leveling.
The master Phase 1 orchestrator for a new tender. Catalogues the tender pack, runs Go/No-Go analysis, extracts compliance requirements, flags contract risks against the active Ailtir profile's playbook (Irish PW-CF/RIAI or UK JCT/NEC4), and generates a 9-tab Bid Plan Workbook and folder structure. Triggered by /ailtir-cowork-plugin:ailtir_bid-planner.
Converts completed project data into structured case studies, and processes tender debriefs to extract learning signals. Triggered by /ailtir-cowork-plugin:ailtir_case-study-generator or debrief mode.
Extracts all ITT requirements into a tracked deliverables matrix. Triggered by /ailtir-cowork-plugin:ailtir_compliance-matrix or when bid-planner runs.
Proactive lifecycle router. Scans every active bid, tells the user what phase each is in, and recommends the next skill to run. Triggered by /ailtir-cowork-plugin:ailtir_conductor, or auto-invoked at the end of ailtir_prime when at least one bid exists.