oc-repo-ops
Repository hygiene and PR readiness gate. Invoked by oc-git-ops before every PR and after oc-docs-forge generates the PR documentation packet. Use for /oc-repo, /oc-repo audit, /oc-repo verify, "repo hygiene", "clean this repo", "is this PR ready", "check generated files", "catalog drift", "plugin/cache drift", ".gitignore policy", orphaned docs/files, stale generated artifacts, source-vs-doc mismatch, or any repository cleanliness question.
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Repo Ops
- Command Reference
- Every-PR Gate
- /oc-repo audit
- /oc-repo verify
- /oc-repo clean
- /oc-repo catalog
- Checkpoint Integration
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. 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 gittreeprojection (excluding .checkpoints/) under policy pr-readiness-v1, in the branch's own file .checkpoints/handoffs/pr-readiness-v1/ .json. Opchain's Git Ops flow and requested CI wiring consume it through scripts/lib/release-evidence.mjs; missing, stale
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- asfbay-bit/opchain-skills
- Source file
- plugins/opchain/skills/oc-repo-ops/SKILL.md
- Fixed revision
- 1c7c7bd69a7d875a5dffb419911c24752ca6c285
Requirements
- Only the author’s Skill metadata is included. Read the full instructions to check dependencies, licensing and conditions of use.
A small first task
先阅读原作者说明，再决定是否在自己的 AI 工具中使用。
Instructions for your AI tool
- Claude Desktop: resource-specific guide not available yet
- Claude Code: resource-specific guide not available yet
- Cursor: resource-specific guide not available yet
- Codex: resource-specific guide not available yet
Author documentation is not live verification by this site. Without evidence, we do not mark a resource as compatible, safe or free.
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: asfbay-bit/opchain-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T17:01:27.001Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.