github

Automate GitHub repository operations using the gh CLI.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/hammadparveez/mrhammadclaw --skill github-hammadparveez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/hammadparveez/mrhammadclaw/tree/main/skills/github
Command: npx skills add https://github.com/hammadparveez/mrhammadclaw --skill github-hammadparveez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines interactions with GitHub repositories by leveraging the official gh CLI, automating tasks related to issues, pull requests, and CI/CD workflows.

Core Features & Use Cases

  • Issue Management: Create, list, and close GitHub issues.
  • Pull Request Operations: List, view, check CI status, and merge pull requests.
  • CI/Workflow Monitoring: View recent CI runs, specific run logs, and re-run failed jobs.
  • API Queries: Fetch repository data, labels, and stats using the GitHub API.
  • Use Case: Quickly check the CI status of a specific pull request or create a new issue to report a bug.

Quick Start

Use the github skill to list all open issues for the repository owner/repo.

Frequently Asked Questions about github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the CI status of a pull request using the GitHub CLI?

To check CI status of a pull request, the GitHub CLI queries repository workflows and returns the current pipeline state for the targeted branch. You can view recent CI runs, check specific PR statuses, and access run logs directly.

How do I create and close GitHub issues automatically via the command line?

Creating and closing GitHub issues is handled by executing `gh` CLI commands to automate repository operations. The process lists open issues, creates new bug reports, and closes resolved tickets without leaving the terminal.

Can I monitor and re-run failed CI/CD pipeline jobs directly from the terminal?

Monitoring CI/CD pipelines from the terminal allows you to view recent workflow runs and fetch specific run logs. If jobs fail, you can trigger a re-run directly via GitHub CLI commands to validate pipeline changes.

Do I need to authenticate the gh CLI before managing pull requests and issues?

Yes, authenticating the `gh` CLI is required before managing pull requests or issues. You must configure repository access credentials beforehand to ensure the GitHub API queries and CI monitoring commands execute successfully.

What is the best way to fetch repository data and labels using the GitHub API?

Fetching repository data and labels is done by leveraging the GitHub API through the `gh` CLI. This approach queries repository stats, retrieves label configurations, and extracts repository metadata programmatically.

How do I list and merge pull requests using the GitHub CLI?

Listing and merging pull requests is executed through `gh` CLI commands that query repository branches. The operation lists open PRs, views diff details, checks CI status, and merges approved changes into the target branch.