gh

What This Skill Does

The GitHub CLI (gh) skill provides a powerful interface for interacting with GitHub repositories directly from your terminal or OpenClaw environment. It simplifies the developer workflow by enabling the execution of complex Git and GitHub operations without needing to navigate the web browser. From repository management to issue tracking and pull request workflows, this skill allows users to maintain full control over their source code, project management, and collaborative tasks. It is designed to be idempotent and scriptable, making it a reliable tool for automating repetitive tasks.

Installation

To integrate this tool into your environment, run the following command within your terminal or OpenClaw management console: clawhub install openclaw/skills/skills/trumppo/gh. Ensure you have the GitHub CLI installed on your machine and have authenticated via gh auth login before attempting to use this skill, as it relies on the underlying local configuration for API access.

Use Cases

This skill is ideal for developers who spend a significant portion of their time managing GitHub infrastructure. Common scenarios include automatically creating a new repository with default security settings (private by default), branching off existing projects via cloning or forking, and managing large volumes of issues. Furthermore, it shines during the code review process, allowing users to list, view, and merge pull requests efficiently. By using the CLI approach, teams can standardize their delivery pipeline and ensure that every release or feature branch follows consistent naming conventions and documentation standards.

Example Prompts

1. "OpenClaw, use gh to create a new private repository called 'project-alpha' with a description about my new Python framework."
2. "List the top 10 open issues for the current repository and comment on issue number 42 with the text: 'I am currently working on this bug, expect a fix soon.'"
3. "Open the most recent pull request in my default browser so I can review the changes before merging."

Tips & Limitations

To maximize effectiveness, always verify your current repository context using gh repo view before running commands that modify state. Since this skill interacts directly with the GitHub API, ensure you have the necessary permissions for the targeted repository, especially when attempting to delete branches or merge pull requests. For safety, always include the --confirm flag in scripts to prevent unexpected interactive prompts. Note that this skill requires an active internet connection and authorized GitHub credentials. Be cautious with commands that modify repository settings, as these actions may be permanent; verify the target branch and repository owner before executing destructive actions.