Agent skill
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 this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/gh-dvcrn-openclaw-skills-mark
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
--privateis set on create. - Prefer
--confirmto avoid interactive prompts in automation.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?