oc-git-ops

Topics in the source

• Git Ops
• /oc-git — Command Reference
• How This Skill Works
• Phase 0: Repository Setup ("set up the repo")
• First Time
• Returning (repo already cloned)
• Authentication
• Branch Naming Convention

On first invocation, read references/orchestrator.md and follow its welcome protocol. Move code from Claude's workspace to a git repository with proper branch management, commit structure, and PR descriptions. This is the bridge between "Claude built it" and "it's in version control." When the user types /oc-git, display this menu: Plain requests, not slash commands: "set up the repo" (clone and prepare the workspace, Phase 0), "git status" (branch, staged changes, remote state and diff since the last commit), and "show / set the git conventions" (branch and commit naming). -- The typical flow: 1. Clone the user's repo (or confirm it's already cloned) 2. Create a feature branch following project conventions 3. Copy/move built files into the repo working tree 4. Stage each intended commit and run oc-bug-check; an enrolled Git hook verifies the exact staged candidate and its immutable PASS receipt at each commit 5. Make structured commits (one per logical unit) 6. Push the branch 7. Run the pre-PR gate: oc-docs-forge (PR docs packet) → oc-repo-ops (readiness check); docs edits the packet makes are committed (through the bug-check gate) and pushed before the readiness check 8. Generat

This is an excerpt. Refer to the complete source and its current requirements.