メニュー
Bumps the BreakEscape gem version and keeps Gemfile.lock in sync. Trigger when the user asks to "bump the version", "release a new version", "increment the version", or "update the version number".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Full design review of a Break Escape scenario — runs the validator script then applies higher-level design judgement from README_scenario_design.md. Trigger when the user explicitly asks for a "design review", "full review", "deep review", or "scenario critique", or when the validate-scenario skill has already been run and the user wants to go deeper.
Runs the Break Escape scenario validator script and reports errors and warnings. Trigger when the user asks to "validate", "check the scenario", "run the validator", or "are there any errors". Lighter touch than scenario-design-review — focuses on what's broken rather than what could be better.
Produces a QA walkthrough of a Break Escape scenario — a numbered checklist of player actions on the critical path, with expected outcomes. Reconciles the walkthrough against the dungeon graph to catch missing dependencies or undocumented requirements. Trigger when the user asks for a "walkthrough", "QA script", "how to complete the scenario", or "critical path trace".
Runs the scenario validator and opens the generated dungeon graph for a Break Escape scenario file (.json or .json.erb). Use this skill whenever the user asks for a diagram, graph, map, dependency chart, or visual overview of a scenario's lock/key structure. Also trigger when the user asks to "visualise the mission", "show the lock and key structure", "draw the dungeon graph", "update the diagram", or "confirm the graph is up to date" after editing a scenario.
SOC 職業分類に基づく
| name | bump-version |
| description | Bumps the BreakEscape gem version and keeps Gemfile.lock in sync. Trigger when the user asks to "bump the version", "release a new version", "increment the version", or "update the version number". |
Update the version in the one canonical place and regenerate the lockfile so CI doesn't fail.
If the user specified a version, use it. Otherwise read the current version and increment the patch number (third digit), e.g. 1.0.4 → 1.0.5:
cat lib/break_escape/version.rb
Edit lib/break_escape/version.rb — change only the VERSION constant string. Do not touch ASSETS_VERSION.
The PATH section of Gemfile.lock embeds the gem version. After changing VERSION, it will be out of sync and CI will fail with "The gemspecs for path gems changed" in deployment mode.
Update it directly — change only the version on the break_escape (X.Y.Z) line in the PATH block:
PATH
remote: .
specs:
break_escape (1.0.5) ← update this line
Do not run bundle install — the global ~/.bundle/config has a mirror pointing to a local Hacktivity cache path that doesn't exist, which causes bundle install to fail in this project.
Tell the user:
Gemfile.lock was updated (show the new PATH block)Suggest a commit message like: chore: bump version to X.Y.Z