Menu
Migrates older Claude/Codex workflow repos to the current tasks-first harness while preserving or archiving user-authored docs and hooks.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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-migrate |
| description | Migrates older Claude/Codex workflow repos to the current tasks-first harness while preserving or archiving user-authored docs and hooks. |
| when_to_use | repo-harness-migrate, migrate legacy Claude repo, migrate docs/TODO.md, migrate docs/PROGRESS.md, legacy workflow docs |
Use this command when inspection finds legacy workflow docs or stale harness artifacts.
bun scripts/inspect-project-state.ts --repo <repo> --format text.bun scripts/migrate-workflow-docs.ts --repo <repo> --dry-run when legacy docs exist.bash scripts/migrate-project-template.sh --repo <repo> --apply.known_generated files and preserves user-authored legacy content.mode: initialize, route to repo-harness-init.mode: audit with no drift, route to repo-harness-check or repo-harness-upgrade.ownership=known_generated by the workflow contract.