Menú
Adds or syncs explicit repo-local capability boundaries without running full repo-harness init, migrate, or upgrade.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación 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.
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-capability |
| description | Adds or syncs explicit repo-local capability boundaries without running full repo-harness init, migrate, or upgrade. |
| when_to_use | repo-harness-capability, add capability, add capacity, configure capability, only add selected capabilities, add subfolder AGENTS.md, add subfolder CLAUDE.md |
Use this command when the repo already has the repo-harness harness and the user wants to add selected capability boundaries without refreshing the full harness.
bun scripts/inspect-project-state.ts --repo <repo> --format text when available to confirm the harness exists.bun scripts/capability-config.ts add --repo <repo> --prefix <path>--id, --domain, --name, and --verification-hint values when the inferred names would be unclear.bun scripts/capability-resolver.ts validate --repo <repo> --format textbun scripts/capability-resolver.ts match --repo <repo> --path <path> --format jsonrepo-harness-init.scripts/migrate-project-template.sh --apply.AGENTS.md and CLAUDE.md contract files only for requested capabilities.--create-prefix only when the user explicitly wants the missing directory created.