/repo-harness-chatgpt
Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, MCP Connector setup, MCP bridge planning handoff, and Connector invocation read-back evidence.
$ npx -y skills add Ancienttwo/repo-harness --skill repo-harness-chatgpt --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/repo-harness-chatgpt
Context preview
The summary Claude sees to decide when to auto-load this skill.
Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, MCP Connector setup, MCP bridge planning handoff, and Connector invocation read-back evidence.
SKILL.md
repo-harness-chatgpt.SKILL.mdname: repo-harness-chatgpt
description: Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, MCP Connector setup, MCP bridge planning handoff, and Connector invocation read-back evidence.
when_to_use: "repo-harness-chatgpt, ChatGPT Web consult, GPT Pro consult, gptpro, browser GPT, ChatGPT MCP Connector, ChatGPT bridge, MCP read-back, GPT Pro delegate, delegate to ChatGPT, 外包给 GPT"
repo-harness-chatgpt
Canonical rule owner for every repo-harness ChatGPT integration surface: Oracle browser consult, session continuation, MCP Connector/bridge setup and operation, and MCP invocation read-back evidence. Discoverable only after explicit ChatGPT setup; never implied by either install profile. Router-only: mode protocol lives under `references/`.
Mode Selection
- First-time Oracle browser or MCP Connector configuration -> `references/setup.md`.
- Start a new local -> ChatGPT Web browser consult -> `references/consult.md`.
- Continue, read, or clean up a saved browser session -> `references/continue.md`.
- Verify or accept a ChatGPT MCP tool call as real evidence -> `references/read-back.md`.
- Operate the MCP Connector bridge (planner/executor/orchestrator/coding) -> `references/bridge.md`.
- Delegate a self-contained task to GPT Pro and independently accept the result -> `references/delegate.md`.
Boundaries
- Product planning never implies this package; ChatGPT discovery requires explicit setup.
- Never request or handle ChatGPT passwords, 2FA codes, cookies, browser storage, or session tokens; login/captcha/SSO stop and hand back to the user.
- Setup, consult, and bridge modes share these safety rules by reference; none shares secrets, auth state, or tokens with another mode.
- Consult stays planning/review/critique only, never the code-edit executor; delegate is the sole approved path for code deliverables, and GPT Pro still never executes edits.
- A missing or unreadable canonical reference fails the calling command closed; it never synthesizes replacement prose.
- Do not enable remote CDP or an orchestrator dev runner unless the user explicitly asks and the boundary is documented.
Read more
name: repo-harness-chatgpt description: Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, MCP Connector setup, MCP bridge planning handoff, and Connector invocation read-back evidence. when_to_use: "repo-harness-chatgpt, ChatGPT Web consult, GPT Pro consult, gptpro, browser GPT, ChatGPT MCP Connector, ChatGPT bridge, MCP read-back, GPT Pro delegate, delegate to ChatGPT, 外包给 GPT"
repo-harness-chatgpt
Canonical rule owner for every repo-harness ChatGPT integration surface: Oracle browser consult, session continuation, MCP Connector/bridge setup and operation, and MCP invocation read-back evidence. Discoverable only after explicit ChatGPT setup; never implied by either install profile. Router-only: mode protocol lives under `references/`.
Mode Selection
- First-time Oracle browser or MCP Connector configuration -> `references/setup.md`.
- Start a new local -> ChatGPT Web browser consult -> `references/consult.md`.
- Continue, read, or clean up a saved browser session -> `references/continue.md`.
- Verify or accept a ChatGPT MCP tool call as real evidence -> `references/read-back.md`.
- Operate the MCP Connector bridge (planner/executor/orchestrator/coding) -> `references/bridge.md`.
- Delegate a self-contained task to GPT Pro and independently accept the result -> `references/delegate.md`.
Boundaries
- Product planning never implies this package; ChatGPT discovery requires explicit setup.
- Never request or handle ChatGPT passwords, 2FA codes, cookies, browser storage, or session tokens; login/captcha/SSO stop and hand back to the user.
- Setup, consult, and bridge modes share these safety rules by reference; none shares secrets, auth state, or tokens with another mode.
- Consult stays planning/review/critique only, never the code-edit executor; delegate is the sole approved path for code deliverables, and GPT Pro still never executes edits.
- A missing or unreadable canonical reference fails the calling command closed; it never synthesizes replacement prose.
- Do not enable remote CDP or an orchestrator dev runner unless the user explicitly asks and the boundary is documented.
File-backed workflow harness for reliable Claude Code and Codex sessions.
Repo: Ancienttwo/repo-harness
Other skills on repo-harness.
- /claude-plan
Get an independent architecture/implementation plan from Anthropic Claude (Fable, a different vendor's model) running Claude Code's native plan mode, from inside a non-Claude host such as Codex. Use mid-execution when work hits a genuine design fork or high-stakes decision that
Open skill - /repo-harness-cross-review
Independent cross-model review of the current review scope (branch diff plus staged, unstaged, untracked changes) from the opposite vendor's model. Catches spec drift, missing edge cases, and fake tests self-review cannot see. Use before merging, after a tricky change, or a
Open skill - /repo-harness-plan
Interactive planning entrypoint for repo-local agentic development work. Produces an approved plan before implementation, and reviews an existing plan across product, engineering, design, and DevEx dimensions.
Open skill - /repo-harness-product
Canonical rule owner for PRD drafting, Sprint planning/execution, and native Goal-session preparation from repo-harness planning artifacts.
Open skill - /repo-harness-setup
Canonical rule owner for installing, migrating, upgrading, repairing, scaffolding, and capability-configuring the repo-harness workflow in a repository.
Open skill