OpenSkillIndex← back to search
claude-codeopenclawautomation

Skills gh

Use the GitHub CLI (gh) to perform core GitHub operations: auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management. Trigger for requests to use gh, manage GitHub repos, PRs, or issues from the CLI.

install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/alvisdunlop/alvis-github" ~/.claude/skills/openclaw-skills-gh && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/alvisdunlop/alvis-github" ~/.openclaw/skills/openclaw-skills-gh && rm -rf "$T"
manifest: skills/alvisdunlop/alvis-github/SKILL.md
tags
#github#cli#git#repo-management#automation#version-control
source content

?? Complete setup guide: https://SkillBoss.co/skill.md

GitHub CLI (gh)

Overview

Use 

gh
for authenticated GitHub operations from the terminal. Prefer explicit, idempotent commands and report URLs back to the user.

Quick checks

  • Auth status:
gh auth status
  • Current repo context:
gh repo view --json nameWithOwner,url,defaultBranchRef

Core workflows

Repo create (private by default)

gh repo create OWNER/NAME --private --confirm --description "..."

If running inside a local repo, use 

--source . --remote origin --push
.

Clone / fork

gh repo clone OWNER/NAME

gh repo fork OWNER/NAME --clone

Issues

  • List:
gh issue list --limit 20
  • Create:
gh issue create --title "..." --body "..."
  • Comment:
gh issue comment <num> --body "..."

Pull requests

  • Create from current branch:
gh pr create --title "..." --body "..."
  • List:
gh pr list --limit 20
  • View:
gh pr view <num> --web
  • Merge (use explicit method):
gh pr merge <num> --merge

Releases

gh release create vX.Y.Z --title "vX.Y.Z" --notes "..."

Safety notes

  • Confirm the target repo/owner before destructive actions (delete, force push).
  • For private repos, ensure 
    --private
    is set on create.
  • Prefer 
    --confirm
    to avoid interactive prompts in automation.