Menü
Resolves repo-harness architecture drift requests and updates architecture docs or diagrams without running full init, migrate, or upgrade.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
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.
Verification entrypoint for repo-harness workflow readiness. Runs workflow gates, task sync, contract checks, inspector, and migration dry-run before merge or release.
| name | repo-harness-architecture |
| description | Resolves repo-harness architecture drift requests and updates architecture docs or diagrams without running full init, migrate, or upgrade. |
| when_to_use | repo-harness-architecture, architecture drift, architecture doc, architecture diagram, update architecture index, resolve architecture request |
Use this command when the harness already exists and the user wants a focused architecture documentation, drift-request, or diagram pass.
docs/architecture/index.md and pending files under docs/architecture/requests/.bun scripts/capability-resolver.ts match --repo <repo> --path <path> --format jsondocs/architecture/index.mddocs/architecture/docs/architecture/diagrams/mermaid only for optional human-readable HTML renderings grounded in observed repo files.bash scripts/archive-architecture-request.sh --request <request> --status <resolved|superseded|rejected|no-change> --artifact <path> --note <text>bash scripts/check-architecture-sync.shbun scripts/capability-resolver.ts validate --repo <repo> --format textbash .ai/harness/scripts/check-task-workflow.sh --strict when repo workflow surfaces changedno-change and do not invent one.check-architecture-sync.sh blocks in strict mode, resolve or archive the pending request card for the touched capability before finishing the worktree.scripts/migrate-project-template.sh --apply.mermaid; it remains an external installed skill for optional human-readable HTML.docs/architecture/requests/ pending-only by archiving handled requests.