omc-gh-setup

OMC GitHub Setup

Configure GitHub integration for the current project. Detects the owner and repo from the git remote URL, verifies gh authentication, and writes .omg/config.json with all required settings.

When this skill is invoked, immediately execute the workflow below. Do not only restate or summarize these instructions back to the user.

Trigger Patterns

• "gh setup"
• "github setup"
• "configure github"
• "connect to github"
• "omc-gh-setup"

Prerequisites

Before running the main workflow, verify all prerequisites are present. If any fail, report the issue and stop with actionable remediation steps.

Check 1: gh CLI installed

gh --version 2>&1 | head -1

If this fails: tell the user to install the GitHub CLI from https://cli.github.com/.

Check 2: gh authentication status

gh auth status 2>&1

If this fails or shows "not logged in": tell the user to run gh auth login and retry.

Check 3: Token scopes

gh auth status 2>&1 | grep -i "token scopes"

The token must include the repo scope for full access. If scopes are insufficient, suggest: gh auth refresh -s repo.

---

Step 1: Detect GitHub Remote

Inspect the git remote URL to determine if the repo is hosted on GitHub.

git remote -v 2>&1

GitHub remote URLs follow these patterns:

• https://github.com/{owner}/{repo}.git
• https://github.com/{owner}/{repo}
• [email protected]:{owner}/{repo}.git

Parse the remote URL to extract:

• owner — the GitHub organization or user
• repo — the repository name (strip trailing .git if present)

If no GitHub remote is detected, inform the user and ask whether they want to configure manually (prompt for owner, repo values).

---

Step 2: Probe Existing Configuration

Check if .omg/config.json already exists:

node -e "const f=require('fs');try{process.stdout.write(f.readFileSync('.omg/config.json','utf8'))}catch{console.log('NOT_FOUND')}"

If it exists and contains github settings, ask the user whether to update or keep the existing configuration (use AskUserQuestion).