oc-docs-forge
Documentation creation, standardization, and upkeep for every PR. Invoked by oc-git-ops before PR creation and by release flows before release PRs. Use for /oc-docs, /oc-docs pr, "generate the PR docs", "update README", "standardize docs", "refresh product documentation", "write PR body docs", "post a PR docs comment", "docs upkeep", changelog/ADR/readme drift, or any request where implementation changes need reader-facing documentation. Catalog drift (generated catalogs out of sync with source) is oc-repo-ops.
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
- Docs Forge
- Command Reference
- Every-PR Contract
- /oc-docs pr
- /oc-docs readme
- /oc-docs standardize
- /oc-docs upkeep
- /oc-docs verify
On first invocation, read references/orchestrator.md and follow its welcome protocol. Docs Forge turns a code change into the documentation that must travel with it. It owns the content, wording, placement, and freshness checks for PR bodies, PR comments, README/catalog docs, product docs, ADRs, changelog notes, and linked ticket summaries. Boundary: Docs Forge writes and verifies documentation. Repo Ops decides whether the repository is clean enough to open the PR. Git Ops creates the branch, commit, push, and PR after these gates pass. Every PR must contain Docs Forge output in at least one visible surface: 1. The PR body, for normal documentation packets. 2. A PR comment with marker , when the documentation packet is too long for the body. 3. Both the body and a comment, when the body needs a compact summary and the comment carries migration notes, screenshots, large tables, or generated docs. The PR body must always include a ## Documentation section. If no user-facing documentation changed, say so explicitly and explain why. Silence is not a pass. Read references/pr-documentation-packet.md before generating or verifying PR documentation. Inputs: git diff --stat and changed fil
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-docs-forge/SKILL.md
- Fixed revision
- 1c7c7bd69a7d875a5dffb419911c24752ca6c285
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:26.910Z.
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.