name: gh-cli version: 0.1.0 description: GitHub CLI wrapper - create repos, manage issues/PRs, check CI status. Already installed and authenticated. homepage: https://cli.github.com metadata: {"openclaw":{"emoji":"🐙","requires":{"bins":["gh"]},"category":"devops"}}

GitHub CLI (gh)

Full GitHub access via command line. Already authenticated.

Status

gh auth status

Current: ✅ Authenticated as shalomolahs
Token: gho_************************************
Scopes: gist, read:org, repo
Config: /root/.config/gh/hosts.yml

When to Use This Skill

Use gh when you need to:

• Create repositories (faster than web UI)
• Push code to MoikasLabs org
• Manage issues/PRs programmatically
• Check CI status on PRs
• Work with GitHub Actions

Quick Reference

Repositories

# Create new repo
gh repo create MoikasLabs/repo-name --public --description "What it does"

# Create and push local code
gh repo create MoikasLabs/repo-name --public --source=. --push

# Clone existing repo
gh repo clone MoikasLabs/existing-repo

# View repo in browser
gh repo view MoikasLabs/repo-name --web

Issues

# Create issue
gh issue create --repo MoikasLabs/repo-name \
  --title "Feature: Add X" \
  --body "Details about the feature..."

# List issues
gh issue list --repo MoikasLabs/repo-name --limit 10

# View issue
gh issue view 42 --repo MoikasLabs/repo-name

Pull Requests

# Create PR
gh pr create --repo MoikasLabs/repo-name \
  --title "Add feature X" \
  --body "What changed and why..."

# Check PR status
gh pr status --repo MoikasLabs/repo-name

# View PR checks (CI)
gh pr checks 55 --repo MoikasLabs/repo-name

# Merge PR
gh pr merge 55 --repo MoikasLabs/repo-name --squash

GitHub Actions

# List recent workflow runs
gh run list --repo MoikasLabs/repo-name --limit 10

# View specific run
gh run view 1234567890 --repo MoikasLabs/repo-name

# Watch live logs
gh run watch 1234567890 --repo MoikasLabs/repo-name

API Access

# Direct API calls
gh api repos/MoikasLabs/repo-name/issues
gh api repos/MoikasLabs/repo-name/pulls

Common Workflows

Create New Skill Repo

# In the skill directory
cd /root/dev/moikaslabs/new-skill

git init
git add .
git commit -m "Initial commit"

# Create repo on GitHub and push
gh repo create MoikasLabs/new-skill --public --source=. --push

Push Existing Code

# Already has git history
git remote add origin https://github.com/MoikasLabs/repo-name.git
git push -u origin master

# Or using gh shorthand
gh repo clone MoikasLabs/repo-name  # if starting fresh

Create Issue from Task

gh issue create --repo MoikasLabs/target-repo \
  --title "TASK: Implement team broadcast for custom roles" \
  --body "From team-orchestrator skill. Need to filter by role prefix."

Authentication Details

Account: shalomolahs (Shalom)
Org Access: MoikasLabs ✅ (via read:org scope)
Repo Permissions: Full (read/write) ✅
Token Location: /root/.config/gh/hosts.yml

If auth expires:

gh auth login
# Or with token:
echo $GITHUB_TOKEN | gh auth login --with-token

Troubleshooting

"Repository not found"

• Check org name: MoikasLabs not moikaslabs
• Verify token has repo scope: gh auth status

"Authentication failed"

gh auth status        # Check current auth
gh auth refresh       # Refresh token
gh auth login         # Re-authenticate

Push rejected

# Force push (careful!)
git push --force-with-lease origin master

# Or update first
git pull origin master --rebase
git push origin master

🚦 Git Workflow Best Practices

NEVER merge directly to master. Always use Pull Request workflow.

The Rule

❌ WRONG: git checkout master && git merge feature/X && git push
✅ RIGHT:  gh pr create → gh pr review → gh pr merge

Feature Branch Workflow

# 1. Start from fresh master
git checkout master
git pull origin master

# 2. Create feature branch
git checkout -b feature/descriptive-name
git push -u origin feature/descriptive-name

# 3. Implement and commit
git add .
git commit -m "feat: Add specific feature"
git push origin feature/descriptive-name

# 4. Create Pull Request (NEVER skip this!)
gh pr create \
  --title "feat: Add dashboard component" \
  --body "## Changes
- Implementation details
- Testing notes" \
  --base master

# 5. Wait for review (self-review at minimum)
gh pr checks  # Ensure CI passes
gh pr view    # Review your own work

# 6. Merge via PR only
gh pr merge <number> --squash

# 7. Cleanup
git branch -d feature/descriptive-name
git push origin --delete feature/descriptive-name

PR Title Conventions

| Prefix | Use For | Example | |--------|---------|---------| | feat: | New feature | feat: Add session monitor | | fix: | Bug fix | fix: Resolve WebSocket reconnect | | docs: | Documentation | docs: Update README | | refactor: | Restructure | refactor: Extract components | | test: | Tests | test: Add unit tests |

Common PR Commands

# Create PR
git checkout feature/my-feature
git push origin feature/my-feature
gh pr create --title "feat: Add X" --base master

# Check PR status
gh pr status                    # All your PRs
gh pr checks 42                 # CI status for PR #42
gh pr view 42                   # View PR details

# Review and merge
gh pr diff 42                   # See changes
gh pr merge 42 --squash         # Merge (only via PR!)
gh pr merge 42 --squash --auto  # Auto-merge when CI passes

# List and manage
gh pr list --repo MoikasLabs/shalom-ui
gh pr close 42                  # Close without merging

Handling Merge Conflicts

# Update your feature branch with latest master
git checkout feature/my-feature
git fetch origin
git rebase origin/master

# Fix conflicts in files, then:
git add <resolved-files>
git rebase --continue
git push --force-with-lease origin feature/my-feature

Team Coordination with Agents

When spawning agents that will push code:

# Spawn with explicit PR requirement
team spawn cio --name "implement-fix" \
  --task "Implement fix in feature branch, create PR, DO NOT merge directly"

# Agent must report:
# - Branch: feature/fix-X
# - PR: #43 created
# - Ready for review

# You review and merge:
gh pr view 43
gh pr checks 43
gh pr merge 43 --squash

Emergency Exceptions (Document Why!)

Only bypass PR if:

• CI/CD is completely down
• Critical production hotfix needed NOW
• Solo project with no reviewer available

# If you MUST merge directly (emergency only):
git checkout master
git merge --no-ff feature/hotfix -m "HOTFIX: Emergency merge PR #44 [reason]"
git push origin master

# Create retroactive PR for audit trail:
gh pr create --title "HOTFIX RETRO: [description]" \
  --body "Merged directly due to [emergency reason]"

Worktree + PR Integration

# Create isolated worktree for feature
git worktree add ../worktree/feature-X feature/descriptive-name
cd ../worktree/feature-X

# Implement in isolation
# Test independently
# Commit and push

# Create PR from worktree
git push origin feature/descriptive-name
cd /root/dev/shalom-ui  # Back to main repo
gh pr create --title "feat: Add X" --head feature/descriptive-name

# After PR merges, cleanup
git worktree remove ../worktree/feature-X
git branch -d feature/descriptive-name

Integration with Other Skills

After team-orchestrator creates code

cd /root/dev/moikaslabs/new-skill
./install.sh
git add -A
git commit -m "feat: Initial skill implementation"
git push -u origin master

# Create PR for review (even if solo)
gh pr create --title "feat: New team-orchestrator skill" --base main

Check CI before merging

gh pr checks 42 --repo MoikasLabs/shalom-ui
# All green? Merge:
gh pr merge 42 --repo MoikasLabs/shalom-ui --squash
team pr cleanup feature-name  # Delete branch and worktree

Automated PR creation from agent

# Agent creates PR after implementation
cd /root/dev/shalom-worktree/agent-work
git add -A
git commit -m "feat: Add component as specified"
git push origin feature/agent-work

# Create PR via gh CLI
gh pr create \
  --title "feat: $(git branch --show-current | sed 's/feature\///')" \
  --body "Implementation by $(whoami)
  
  ## Changes
  - $(git log --oneline -1 | cut -d' ' -f2-)
  
  ## Testing
  - [ ] Verified locally
  - [ ] Build passes" \
  --base master

# Report back: PR #X created, ready for review

Summary: The Golden Rules

1. Never push to master directly — always via PR
2. Never git merge on local master — always gh pr merge
3. Self-review before requesting review — check your own diff
4. Keep feature branches short-lived — merge within days, not weeks
5. Delete branches after merge — keep repo clean
6. Use conventional commits — feat:, fix:, docs:
7. Document emergency exceptions — if you must bypass PR, explain why

Already authenticated. Use PR workflow always. 🐙