repo-harness-upgrade
Refreshes an already-installed repo-harness harness using manifest-owned upgrade actions from assets/workflow-contract.v1.json.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Refreshes an already-installed repo-harness harness using manifest-owned upgrade actions from assets/workflow-contract.v1.json.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
routes repo-harness requests through the CLI and hook automation plugin for init, update, scaffold, migrate, audit, repair, and ship workflows
Use when setting up or operating the repo-harness ChatGPT Controller, GitHub Issue Launcher, local Agent Runs, or GitHub Copilot cloud sessions.
Use when the user wants Codex to consult their logged-in ChatGPT Web session through repo-harness browser engine for planning, architecture review, PRD critique, or Codex goal generation.
Resolves repo-harness architecture drift requests and updates architecture docs or diagrams without running full init, migrate, or upgrade.
Full repo-harness workflow orchestrator. Reads repo state, drafts a plan, self-reviews twice, executes the approved plan, runs review/check gates, and delegates final PR closeout to repo-harness-ship.
Adds or syncs explicit repo-local capability boundaries without running full repo-harness init, migrate, or upgrade.
| name | repo-harness-upgrade |
| description | Refreshes an already-installed repo-harness harness using manifest-owned upgrade actions from assets/workflow-contract.v1.json. |
| when_to_use | repo-harness-upgrade, upgrade installed harness, refresh repo-harness contract, reconfigure current tasks-first harness, upgrade workflow contract |
Use this command when a repo already has a current harness surface but needs the latest contract, helpers, templates, or policy.
bun scripts/inspect-project-state.ts --repo <repo> --format text.upgrade_plan and assets/workflow-contract.v1.json#migrations.upgrade.actions.repo-harness-migrate.upgrade_plan is empty, report no-op readiness instead of touching files.known_generated surfaces listed by the contract._ref/, _ops/, secrets, local env, custom hooks, and user-authored legacy material.