Repo Ops

On first invocation, read references/orchestrator.md and follow its welcome protocol.

Repo Ops is the repository-level cleanliness gate. It does not write the docs packet itself; Docs Forge does that. Repo Ops verifies that the packet exists, that repo state is clean enough to review, and that generated/catalog/source surfaces agree before Git Ops opens a PR.

Command Reference

REPO OPS COMMANDS

  /oc-repo                 Show this menu
  /oc-repo audit           Read-only repo hygiene sweep
  /oc-repo verify          PR readiness gate, blocks on failures
  /oc-repo clean           Apply safe cleanup fixes
  /oc-repo catalog         Verify catalog, README, registry, package parity
  /oc-repo status          Show last gate verdict

  /checkpoint              Show oc-repo-ops checkpoint

Every-PR Gate

oc-git-ops must invoke Repo Ops before creating every PR. The required order is:

0. Precondition: Bug Check has already passed before every commit on the branch (oc-git-ops runs it before each commit, including a docs-packet commit). If it has not run, or its verdict is stale, chain back to oc-bug-check.
1. Docs Forge generates or verifies the PR documentation packet.
2. Repo Ops verifies repository cleanliness and docs packet presence.
3. Git Ops opens the PR only after Repo Ops passes.

Repo Ops publishes a C-contract verification.verdict handoff for the evaluator’s HEAD git_tree_projection (excluding .checkpoints/) under policy pr-readiness-v1. Opchain’s Git Ops flow and requested CI wiring consume it through scripts/lib/release-evidence.mjs; missing, stale, ambiguous, FAIL, or INCOMPLETE evidence blocks. CI separately reruns A’s candidate verifier on the received commit, so a copied local receipt is not independent verification.

Read references/pr-readiness-gate.md before /oc-repo verify.

/oc-repo audit

Read-only sweep. Report findings without editing files.

Checks:

• Git status, branch, base branch, untracked files, and ignored generated junk.
• .gitignore policy against the project convention.
• Generated artifacts that are missing, stale, or checked in incorrectly.
• Catalog parity: source directories, README tables, registry flags, site catalog, MCP catalog, packaged plugin/cache where configured.
• Documentation parity: Docs Forge checkpoint, PR body fragment, README/product docs, changelog/ADR expectations.
• Checkpoint consistency: stale pointers, generated files that no longer exist, contradictory checkpoint-vs-git state.
• Large/binary artifacts, local logs, temp files, screenshots, and accidental secrets that should not be in the PR.

/oc-repo verify

PR readiness gate. Fail closed on:

• Missing or stale .checkpoints/oc-docs-forge.checkpoint.json. Stale means its skill_state.verified_for_sha is not the HEAD of the branch being verified — the same binding oc-release-ops’ verify gate uses for the docs row — or its checkpoint status is blocked (a failed /oc-docs verify).
• Missing ## Documentation PR body fragment.
• Required docs update absent from the diff and no explicit follow-up.
• Catalog/source drift for surfaces affected by the PR.
• Generated files out of sync with source.
• Dirty untracked files that look related to the PR but are not staged or intentionally ignored.
• .gitignore rules that contradict project policy.
• Broken internal links in docs touched by the PR.
• Checkpoint pointers to files that no longer exist.

Warnings never block, but they must appear in the PR body or Repo Ops checkpoint. Every run publishes a verification.verdict handoff with candidate kind git_tree_projection, the evaluator-produced SHA-256 identity, policy pr-readiness-v1, and PASS, FAIL, or INCOMPLETE. Excluding .checkpoints/ avoids self-reference. Read the identity with node scripts/lib/release-evidence.mjs --print-candidate --json; skill_state.verified_for_sha remains compatibility output.

/oc-repo clean

Apply safe cleanup fixes:

• Remove obvious temp/log/build artifacts.
• Add missing ignore rules that do not conflict with the checkpoint protocol.
• Regenerate catalogs with existing project scripts.
• Ask Docs Forge to rewrite docs rather than editing large doc surfaces here.

Do not delete user-authored files unless the user explicitly asks or the file is clearly generated and reproducible.

/oc-repo catalog

For Opchain itself, verify:

• skills/*/SKILL.md count matches skills/README.md.
• src/lib/flags/registry.js has one registry flag per skill and command flags for every command verb.
• Generated catalogs are current after npm run gen-catalog and npm run gen-mcp-catalog.
• Skill bundle sync does not drift (npm run sync-bundles:check).
• Plugin skill copy does not drift (npm run sync-plugin-skills:check, which compares plugins/opchain/skills with skills/).

For other repos, infer equivalent catalog surfaces from package scripts, content collections, generated files, and docs.

Checkpoint Integration

The shared checkpoint schema, write rules and resume protocol live in references/checkpoint-protocol.md, bundled with this skill. This section adds only what is specific to oc-repo-ops.

Location: {project-dir}/.checkpoints/oc-repo-ops.checkpoint.json

{
  "skill": "oc-repo-ops",
  "phase": "pr-verify",
  "status": "complete",
  "progress_summary": "Repo readiness gate passed for PR creation.",
  "context_primer": {
    "key_decisions": [
      "Docs Forge packet required before every PR.",
      ".checkpoints/ is tracked in git unless the project checkpoint protocol says otherwise."
    ],
    "generated_files": [
      ".checkpoints/oc-repo-ops.checkpoint.json"
    ]
  },
  "skill_state": {
    "verdict": "PASS",
    "blocking_findings": [],
    "warnings": [],
    "docs_packet_verified": true,
    "catalog_verified": true,
    "generated_artifacts_verified": true,
    "internal_links_verified": true,
    "related_untracked_files_staged": true,
    "verified_for_sha": "abc123",
    "last_verify": {
      "at": "2026-09-11T04:15:18Z",
      "branch": "feat/example",
      "base": "origin/main@abc123",
      "verdict": "PASS",
      "blocking_findings": []
    }
  },
  "handoffs": [{
    "id": "pr-readiness-<candidate-id>",
    "contract_version": "1.0",
    "type": "verification.verdict",
    "created_at": "2026-09-13T20:00:00Z",
    "verified_at": "2026-09-13T20:00:00Z",
    "producer": { "skill": "oc-repo-ops", "run_id": "<run-id>" },
    "candidate": { "kind": "git_tree_projection", "id": "sha256:<digest>" },
    "payload": { "verdict": "PASS", "policy": "pr-readiness-v1" }
  }]
}

Cross-Skill Reads